this post was submitted on 08 Apr 2025
57 points (100.0% liked)

Selfhosted

45974 readers
1553 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
57
How and where should I keep backups of system configurations? (sh.itjust.works)
submitted 1 week ago by someacnt@sh.itjust.works to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] marauding_gibberish142@lemmy.dbzer0.com 15 points 1 week ago (3 children)
  1. Create git repo
  2. Put all config in git repo
  3. Create repo on codeberg
  4. Clone git repo to both VPS and laptop

No extra money needed

[–] tofu@lemmy.nocturnal.garden 7 points 1 week ago (1 children)

Make sure to not check in secrets in plaintext. git crypt is one way to encrypt secrets before checking them in.

[–] marauding_gibberish142@lemmy.dbzer0.com 2 points 1 week ago (1 children)

I suggest SOPS

[–] keen@lemmy.world 0 points 1 week ago (1 children)

Terraform sensitive variables and AWS secrets manager? ^^

[–] marauding_gibberish142@lemmy.dbzer0.com 2 points 1 week ago

I don't like big corporations so I wouldn't do that, but sure

[–] someacnt@sh.itjust.works 3 points 1 week ago

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.

[–] AustralianSimon@lemmy.world -4 points 1 week ago* (last edited 1 week ago) (2 children)

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.

[–] fenndev@leminal.space 18 points 1 week ago (1 children)

Please don't use AI for simple things like this.

The Odin Project has a tutorial on Git Basics and a guide on Setting Up Git. The instructions are roughly the same whether on Github, Codeberg, etc.

Once you have the repository, it's as simple as:

git add .
git commit -m "Updated config"
git push origin main
[–] Kusimulkku@lemm.ee 2 points 1 week ago

Please don't use AI for simple things like this.

Simple things seems like the best use of AI

[–] marauding_gibberish142@lemmy.dbzer0.com 5 points 1 week ago (1 children)