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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
Personally I just wrote a bash script that does all of my regular updates and I run it manually whenever
And it's stable enough for you? Do you go service by service or is it good enough for everything?
For docker compose I have a part of the script that gets all subdirs of "projects" dir and for each one does an update (that way any new service will be updated without having manually specify in the script) for everything else I just hard coded the update process.
Generally 90% of my updates are just running the script, on the other 10% I do some manual work (like updating configs, etc)
But for the most part this is me refusing to use already existing tools that could probably do most of this better