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
nah you're probably not going to get any benefits from it. The best way to make your setup more maintainable is to start putting your compose/kubernetes configuration in git, if you're not already.
I don't want to derail this thread, but you piqued my interest in something I've always wanted to do, maybe just for the learning aspect, and to see what I could accomplish.
I've always wanted to see if I could have all my docker compose/run files, and various associated files to a git where I could just reinitialize a server, with everything I already have installed previously. So, I could just fire up a script, and have it pull all my config files, docker images, the works from the git, and set up a server with basically one initial script. I have never used github or others of that genre, except for installation instructions for a piece of software, so I'm a little lost on how I would set that up or if there are better options.
Your description does not sound related to git. It sounds more like nix
This: https://nixos.org/?
Nix is great for reproducibility
Yes, and Nix is another bag of worms. My suggestion is first try to backup your Docker compose file and the configuration files, you can define in .gitignore which files or dirs to ignore and not backup. You don't need any automated installation for your server, as it is fairly standard but you can easily do that if you run it as a VM on top of Proxmox and just create a snapshot of your VM.