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
This is the broader direction. I lament the days where everyone can just use shared hosting and never worry about infrastructure, but everything seems to be moving towards larger and larger stacks… and to abstract as much of that away as possible so people can focus on the apps, docker/Kubernetes is playing a larger and larger role.
Which is also why you’re seeing more and more CLI/scripting — so infrastructure pieces that get in the way of development/apps can be abstracted away and managed in a repeatable fashion between deployments. As you start to work with more and more moving pieces, it is generally a good idea to expand your area of expertise beyond just GUI and move into the more scriptable side, so you can gain more control over your stack more effectively.