Shimitar

My database instances downtime is only when the server itself is rebooting. Never had a single downtime in 20+ years beside that.

This is one of the annoying issues with docker, or better, on how docker is abused in production.

The single instance/multiple databases is the correct way to go, docker approach mess up with that.

Rewriting docker files is always a possibility but honestly defies the reason why docker is used by self hosters.

Also beware that some devs will shunt you out of support if you do, specially the apps that ships docker files by default.

Go bare metal if possible, that way you have full control. Do docker for testing up stuff quickly and be flexible at cost of accepting how stuff is packaged by upstream

Two or more ssds, the biggest you can afford, on a j-bod USB3 or USB-C enclosure. Raid them together on Linux software raid. As hardware, I use a power horse laptop, its more practical, but I had it spare. Buy a nice compromise between CPU power and power comsumpion, that depends on your feelings.

And use Gentoo :)

I have documented most of my steps here https://wiki.gardiol.org

Immich is awesome but has flaws. My workflow has improved with syncthing instead.

Main flaw of immich is being container's deployable only which hurts for various reasons, and devs priority are different from mine (that's unacceptable/irony).

Jokes aside, immich is the best app out there to replace google photos.

But immich require containers and some basic features like sub-path support and in general folder/albums recognition is not there and not really planned clearly for the future.

There is a lot of truth in your words.

Unfortunately, things will not change.

At least let's use podman and I will keep fighting for containers being at least optional.

Here goes my experience.

When I started the self hosted trip, I was against containers and tried to avoid them at all costs. Then I learned about containers, and now I still am against containers but less vividly so. I have used them and still use them.

Containers are good for the self hoster because they deliver fast deploy and easy testing of lots of services quickly. They are good for developers because they can provide one common installation approach that reduces greatly user issues and support requests.

But containers also have downsides as well. First of all they make the user dumber. Instead of learning something new, you blindly "compose pull & up" your way. Easy, but it's dumbifier and that's not a good thing. Second, there is a dangerous trend where projects only release containers, and that's bad for freedom of choice (bare metal install, as complex as it might be, need to always be possible) and while I am aware that you can download an image and extract the files inside, that's more an hack than a solution. Third, with containers you are forced to use whatever deployment the devs have chosen for you. Maybe I don't want 10 postgres instances one for each service, or maybe I already have my nginx reverse proxy or so. I have seen projects release different composer files for different scenarios, but at that point I would prefer to deploy on bare metal.

Said so, containers are not avoidable today, so study and embrace them, you will not be disappointed as its a cool piece of tech. But please stay clear of docker and go podman instead. Podman doesn't rely on a potentially insecure socket and does not require an always running daemon. Podman also by default doesn't force you to run services as root which you should never do. Also, networking feels clearer on podman and podman feels more .modern by using nft instead of iptables. Yes most of this can be fixed on docker, but since podman is a drop in replacement, why bother? Also, podman is truly open source while docker, shockingly, its not.

Here is my wiki page on the subject: https://wiki.gardiol.org/doku.php?id=gentoo:containers feel free to read it.

One last thought: updating containers should not be taken lightly. Its so easy and fast that you might be tempted to setup cron jobs or install watchtower, but you will end sooner or later with a broken service and lost data. So backup, always backup, and keep updating with rationale.

Tldr: containers are unavoidable today and are a cool piece of tech worth investigating. Don't blindly use them as there are security issues involved, and I hope the trend of making containers the only way doesn't take hold, because containers also make self hosters dumber and that's not good.

Basta, si usa firefox e basta!

... Serve davvero un'alternativa però

Atmosferic pressure doesn't change as much as air density with temperature, because its not a closed system.

Actually easier to ride faster in summertime due to less dense air in which the cycler will have to move trough...

This is a pretty good approach! I love it

Mmm not sure, not a fan of open source.projects dependent on for-pay service. Not for the money itself, but what when/if the business model fails and the tools end up abandoned?

The 'net is filled with forgotten open source project.

Thanks! There are a couple I didn't know about and now I need to test them!

Digital Film! Thanks for spotting that up.