ch8zer

joined 2 years ago
sorted by: new top controversial old
Backing up IaC in c/selfhosted@lemmy.world
[–] ch8zer@lemmy.ca 2 points 4 days ago* (last edited 4 days ago)

My parents have a NAS! Maybe I set up Tailscale and send it over there…

Although they live 3 streets away from me so I worry it’s not remote enough in case of flood etc

Backing up IaC in c/selfhosted@lemmy.world
[–] ch8zer@lemmy.ca 3 points 4 days ago (1 children)

Honestly, I just run it from the CLI myself.

I’ve wasted too much time fighting with CI and automation that when I migrated to forjego I didn’t bother to put it in again.

Backing up IaC in c/selfhosted@lemmy.world
[–] ch8zer@lemmy.ca 4 points 5 days ago (3 children)

You pretty much got it. I need a quick way to restore the repo and ideally have git do a self backup. Seems like a cheap VPS may be the way to go

16
Backing up IaC (lemmy.ca)
 

Hi all, I have my home lab set up as a single git repo. I’ve got all infrastructure as opentofu / ansible configs, and using git crypt to protect secret files (tofu state, ansible secret values, etc).

How would you back up such a system? Keeping it on my self hosted git creates a circular dependency. I’m hesitant to use a private codeberg repo in case I leak secrets. Just wondering what the rest of you are doing.

[Question] Asking for recommendations regarding cold database storage in c/selfhost@lemmy.ml
[–] ch8zer@lemmy.ca 3 points 2 weeks ago

You could try something S3 based, and do backups by date?

For example, export a subset of the DB and name it accordingly (ie. 2025-04-to-2025-01.tar).

If you do that there are a lot of pretty cheap S3 providers (like Wasabi).

S3 interfaces nicely with RCLONE so you can move providers etc and pull it really quickly.

As an aside, when I looked into something like this the thing that made me hesitate was the time and cost for retrieval from cold storage (like amazon glacier) outweighed the savings.