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:
- 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!
view the rest of the comments
Yeah why wouldn't you want to know how things work!
I obviously don't know you, but to me it seems that a majority of Docker users know how to spin up a container, but have zero knowledge of how to fix issues within their containers, or to create their own for their custom needs.
That's half the point of the container... You let an expert set it up so you don't have to know it on that level. You can manage fast more containers this way.
OK, but I'd rather be the expert.
And I have no troubling spinning up new services, fast. Currently sitting at around ~30 Internet-facing services, 0 docker containers, and reproducing those installs from scratch + restoring backups would be a single command plus waiting 5 minutes.
30, that's cute. I currently have 70 containers running on my home server. That doesn't include any lab I run or the stuff I use at work. Containers make life much easier. I also guarantee you don't know those apps as well as you think you do either. Just being able to install and configure something doesn't mean you know the inner workings of them. I used to do the same thing you do. Eventually, I would rather spend my time doing other things or learning certain things more in-depth and be okay with a working knowledge of others. It can be fun and rewarding to do things the hard way but don't kid yourself and think you're somehow superior for doing it that way.
Containers != services.
I don't think I am better than anyone. I jumped into these comments because docker was pushed as superior, unprompted.
Installing and configuring does not an expert make, agreed; but that's not what I said.
I would say I'm pretty knowledgeable about the things I host though, seeing as I am a contributor and / or package maintainer for a number of them...
Correct, not all containers are for services. I would never say that docker is superior. I would however say that containers are (I can be pedantic too). They're version-controlled, they come with the correct dependencies, etc... There are many reasons why developing with containers is superior and I'm sure you're aware of them already. Everyone is moving to do exactly that. There are always edge cases, but those are few and far between these days.