Sorry for adding to the massive pile of backup-related question, but I could not figure out how to manage backups from existing answers…
I want to backup my VPS setup (think container-defining files, its volumes, and etc configs), but am unsure where to put it. Does keeping these in the VPS itself make sense? If so, how do I create and manage the backup?
Also, I would need a remote copy - what is the good location for this? I wish I could copy to my laptop, but obviously I cannot do that automatically. Should I pay money for a backup? I want to avoid paying lots of money just for backups. Thanks in advance!
- Create git repo
- Put all config in git repo
- Create repo on codeberg
- Clone git repo to both VPS and laptop
No extra money needed
Codeberg sounds like a good way! I was concerned about server config being stored on self-hosted forgejo (which is configured by the very server config), turns out that need not be the case.
Edit: Was asking about the config targetting process for git (not how to use git) and was going to ask an AI to do some googling for me.
https://docs.codeberg.org/getting-started/first-repository/
Follow this, should suffice
deleted by creator
That’s what you just got shown: Shove the configgy bits into Git.
You will likely have to find the configs you want to save first.
I was hoping for a guide to capture said configs with a recommended subset. Not instructions for using git.
So no the guides don’t help with that.
I’ll just stick to my mkdocs repo.
I’d get familiar with deploying these with some infrastructure-as-code tools, and keep a git repo. Ansible is pretty easy to get started with.
If you haven’t played with Pulumi (for configuring cloud services) and Ansible (for local services, shell commands, apt installs etc) you may enjoy them as a way to capture / re-apply configuration.
Lots of good ideas.
I’m a fan of stow-like tools, but there are advantages to using something like Salt (or similar) if you’re dealing with VPSes that share don’t common configs like firewalls. There’s a lot to learn with things like salt/chef/puppet/attune/ansible, whereas something like yas-bdsm, which is what I’m currently using, is literally just:
- Keep your configs in a git repos, in a structure that mirrors your target
- Run a command and it creates symlinks for the destination files
- Commit your changes and push them somewhere. Or just restic-backup the repos.
The config file formats are irrelevant; there’s no transformation logic to learn. Its greatest feature is its simplicity.
Etckeeper
