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
If you want it to not affect other systems, a container is the obvious choice.
If I did not have any constraints, which method would be the best choice? I want to make upgrades as painless as possible as I plan to follow releases to stay up to date.
I’d say this comes down to your experience with Docker (or whatever you use to containerize).
Generally speaking updates are as easy as pulling the updated image, but if something goes wrong you should know how to run commands inside the container, access the database, etc. Containerization can be painful if you don’t work with it everyday, but at the same time it brings so many advantages and it’s not hard to learn.