Selfhosted
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:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I don't understand. Why are they so specific in the Docker Compose? Why not just have a Docker that pulls the latest of each package without requiring the user to copy long strings?
For the exact reason they are posting this. What if some service you are referencing has breaking changes? If you pinpoint the exact version it will have no effect to your project unless you decide (hopefully after some consideration) to upgrade the service version number.
Sorry, I think I'm asking my question poorly, what I mean is instead of
Which clearly requires user interaction, why not take that out of users' hands and just have
Which is effectively what they're using anyway? I can understand freezing on a version when the upstream removes a feature, but that's not happened and even so, why do they need the SHA verification? Sorry if it seems stupid and straight forward, this is the only container I host that does this and so I'm trying to understand it rather than just feel aggrieved by it.
Also, it's best practise to specifically refer to the digest for containers to avoid re-tags resulting in different images. For folks who audit what runs on their infrastructure, digests are the standard way of referring to an image. For Immich, I'd presume that the digest is partially a security thing and partially a "this specific image is known to be working".
Thank you very much for teaching me something new
I wondered about the sha as well but that's good if you really depend on that version. Since immich is still heavily developing, this isn't something I'd focus in the short term. Only if it persists
Ah okay. Thank you for making the time to respond.
Because there is no stable release. Any update can have breaking changes since it is beta software like immich itself.
Thank you very much. I looked at their Github and saw a couple channels for releases and made a poor assumption. Thanks for sharing your insight.
The technology has changed and hence the dockerfile and thus the compose file
I don't get it! But I also elaborated here: https://lemmy.tf/comment/5043780