Ideally, there’d be a simple RPM installer compatible with Alma 9 that I can point to a samba share that holds all the photos, kind of like what I do with Jellyfin. Also nice if it uses an otherwise unused port or I can easily set what port it uses.
My googling is finding a bunch of docker stuff, which always seems needlessly complicated to me vs an RPM… I’m also using a low powered x86 tiny computer to front JellyFin and would like to host this on the same computer vs needing another server.
No, 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.
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 https://damselfly.info/ which looks more like the workflow I am looking to implement.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Docker (better use Podman!) Is, I am afraid, hard to avoid nowadays. I fully agree with you that bare-metal deployment should always be an option.
Its one of my biggest issues with immich/photoprism/librephotos but there is no way around that.
Immich is the only container I have on my system… A necessary evil (joking).
I know containers now, but still don’t like them too much. I am old I am afraid.
But you shouldn’t be FORCED to use containers, that’s my point.
No one is forcing you to use containers for Immich. It’s simply the most robust way to support it for the team.
You can just take a look at the dockerfiles and follow those steps on bare metal.
No, 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 https://damselfly.info/ which looks more like the workflow I am looking to implement.
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.
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.