Comment on Selfhosted photo manager kind of like Jellyfin
Shimitar@feddit.it 6 months agoNo, I am forced to use containers because… There are no instructions for bare-metal installation and they also do not provide any instruction on how to build from sources (and I tried…)
Also, there are no binary releases only docker-compose.
All in all, immich cannot be deployed but with containers.
No choice: not good.
A Dockerfile itself is the instruction set. There is a certain minimum requirement expected from a server admin that differs from end-user requirements.
The ease of docker obfuscates that quite a bit but if you want to go full bare metal (or full AWS or GCS, etc etc) then you need to manage the full admin part as well - including custom deployments.
Indeed I am a quite proficient sysadmin for my home server, while not a professional one.
I didn’t consider a docker file as instructions for bare metal install, thanks for the suggestion. I am currently using podman with immich because its release cycles are too fast for me to catch up otherwise.
I am thinking to experiment with something different from immich because, while its a great tool, it’s “just” (no pun intended) a backup solution for mobile devices and I need something more than that.
I was considering damselfly.info which looks more like the workflow I am looking to implement.
Phrey@lemmy.sdf.org 6 months ago
Like I said, if you follow the dockerfiles you will end up with a similar result on bare metal.
It’s your own decision if you want to deviate from what the developers want to support.
A project doesn’t need to produce binary releases.
Shimitar@feddit.it 6 months ago
It is true that a project doesn’t need to release binaries. But either those or the instructions on how to build from sources I think are somewhat expected.
Said so, I am hosting immich on docker because, specially on such fast evolving and kind of “beta” software its by far the fastest way.