this post was submitted on 10 Apr 2025
16 points (94.4% liked)

Selfhosted

46113 readers
750 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
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] ch8zer@lemmy.ca 4 points 1 week ago (1 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

[–] r0ertel@lemmy.world 2 points 1 week ago (1 children)

For my own curiosity, how do you perform a build? Is it all done in pipelines, kicked off on change? Do you execute the whole infra build each time you release an update?

[–] ch8zer@lemmy.ca 3 points 1 week 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.

[–] r0ertel@lemmy.world 2 points 1 week ago

Same. I have spent way more time troubleshooting a pipeline than it saves. I like the idea of automation but laziness prevails.