![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
I’m in this comment.
I’m in this comment.
And you can self host it!
How are you persisting Immich’s database?
I’ve been remote for over a decade; not going to stop now.
As an advanced technique, you can usually skip the first half of this.
In what regard?
I think you dropped this: \
I definitely trust Proton much more than I trust myself.
If you’re not paying for a service, you’re likely being monetized by watching ads or providing personal data to companies that don’t necessarily have your best interests at heart.
This is a bit out of date. Nowadays, you pay for the service and are monetized by watching ads and providing personal data to companies that definitely don’t have your best interests at heart.
Why would you need to continue using the self-signed certificates for the Cloudflare connection? Just use the valid certificate for all connections.
Damn, where’d you find that deal?
I mean, you don’t have to watch it.
Fuck, now I really want Oreos.
You want to split your domain so it resolves to a private IP internally and a public IP externally. So, your internal DNS server should return internal IPs.
Good point!
Docker network pools are huge by default. I had to change this as well.
This article covers the issue and the solution in detail:
https://straz.to/2021-09-08-docker-address-pools/
If you just want the solution, skip to the section titled How to configure docker to allow >500 bridge networks. I think you’ll need to remake all your networks after making the change, if I remember correctly.
Here’s my config now:
$ sudo cat /etc/docker/daemon.json
{
"default-address-pools": [
{ "base":"172.16.0.0/12", "size":24 },
{ "base":"172.17.0.0/12", "size":24 },
{ "base":"172.18.0.0/12", "size":24 },
{ "base":"172.19.0.0/12", "size":24 },
{ "base":"172.20.0.0/12", "size":24 },
{ "base":"172.21.0.0/12", "size":24 },
{ "base":"172.22.0.0/12", "size":24 },
{ "base":"172.23.0.0/12", "size":24 },
{ "base":"172.24.0.0/12", "size":24 },
{ "base":"172.25.0.0/12", "size":24 },
{ "base":"172.26.0.0/12", "size":24 },
{ "base":"172.27.0.0/12", "size":24 },
{ "base":"172.28.0.0/12", "size":24 },
{ "base":"172.29.0.0/12", "size":24 },
{ "base":"172.30.0.0/12", "size":24 },
{ "base":"172.31.0.0/12", "size":24 }
],
"log-opts": {
"max-size": "1g"
}
}
I still need to get this back up after the database requirement took it down
No, since it would have created atoms, right?
Yes, that would work. Highly recommend installing docker and running in containers. (Except Tailscale, probably; that would be native.)
In addition to what everyone else in this thread has already covered, the credit card issuers benefit from you having that card in your wallet because they charge the merchant for every transaction. So you’re having the merchant pay the credit card company with every swipe, in exchange for whatever benefits the card provides to you.