I use duplicati for docker containers. You just host it in docker and attach all the persistent volumes from the other containers to it, then you can set up backup jobs for each.

Telegram is less private then whatsapp, unless you use the private chats it’s not even encrypted.

I’m from Germany and I could swear this was the one in the waiting Room of my pediatrician.

I believe they usually follow the trail of the ants walking infront of them so when they’re walking in a circle they’ll technically walk in a circle indefinitely.

Until now the easiest experience for me I actually had was Arch. You have to do everything yourself but i found it way easier to fix things in Arch than in any other distro I used.

I don’t think they meant vanilla Linux like vanilla OS, but more as in the vanilla versions of Linux without much on top/proprietary software.

That’s already Windows 11.

Some Youtube-Channels I can recommend, but with varying levels of “noob”-friedlieness. Just watch a few and decide for yourself which can help the most:

https://youtube.com/@DBTechYT

https://youtube.com/@christianlempa

https://youtube.com/@TechnoTim

https://youtube.com/@LearnLinuxTV

https://youtube.com/@linode

As for a reverse proxy, it depends how you want to access your services. If you’re just gonna host your services on docker and then publish ports on the host you can just access them that way. But that way they are of course not encrypted, which in your home LAN can be fine. To really use a reverse proxy you also need to have a way to rewrite or add dns entries in your local network. All the domains and subdomains you’d want to use must point to the reverse proxy which would then forward the requests to the services.

The way I have it configured right now is that I have a reverse proxy on my docker host which has the ports 443 and 80 published on the host, while all the services I use in docker on that host do not have published ports. They’re all then in a network with the reverse proxy so it can forward the requests to the services. That way I can encrypt everything with SSL/TLS and have trusted certificates on everything. I use nginx proxy manager which also handles my certificates.

The really vulnerable open ports are the ones you forward to your router. But you only need those when you want to access services from outside your network. But I would wait on that until you feel comfortable.

Well somebody did

Yeah, Signals response pointing to how their service works and than all the data consisting of only these two things war hilarious.

Meanwhile docker compose: --remove-orphans

I’ve got 7 on gh and 3-4 of them seem like serious developers with jobs. I don’t think I can handle that fame.