

All of its install steps other than docker compose are still containers, or relate to hosting services, or specific managed platforms.
I’m a simple admin who likes to compile, copy to /usr/bin, prep my system user, populate a directory in /etc with all necessary configs, and write my own .service files.
If you like running single binaries in their own Docker instances, more power to you, but it rubs me the wrong way when people try to force that on me.
NB: I’m not above reading a Dockerfile and executing the steps manually, case in point: that’s how I build lemmy_server for my current instance… but the Immich steps are waay too involved, with too much of the software expecting some less than sane defaults for me. I went through it once, left a bad taste in my mouth, so I stopped using Immich.
Edit: Just to be clear, here’s the installation steps for Photofield. That’s what I like to see. “Download a binary, run, config lives at xxx” - delicious. I also don’t mind doing a ./configure and make if they want me to - just don’t bloat my system with an entire duplicate OS.
Finishing a game helps surprisingly well with morale.
Switching engines is a very big task for a game (of that scale) deep in development, and it’s very tedious.