this post was submitted on 29 Jan 2026
118 points (97.6% liked)
Selfhosted
60210 readers
947 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I salute you and wish you the best in never having a dependency conflict.
I've been resolving them since the late 90s, no worries.
I use Debian
https://i.redd.it/si50fqxh05z21.jpg
My worst dependency conflict was a libcurlssl error when trying to build on a precompiled base docker image.
Agreed. Im tired after work. Debian/yunohost is good enough.
At work its hundreds of docker containers but all ci/cd takes care of that.
Isn't that harder?
It depends a lot on what you want to do and a little on what you're used to. It's some configuration overhead so it may not be worth the extra hassle if you're only running a few services (and they don't have dependency conflicts). IME once you pass a certain complexity level it becomes easier to run new services in containers, but if you're not sure how they'd benefit your setup, you're probably fine to not worry about it until it becomes a clear need.
Me too!