I'm curious to know how others version control their private configuration files / docs / wiki. For now, I've created a #Gitea#Docker stack on my home network. Instead of copying the files I want to track into another folder and pushing from there, I've created hard links. Any other suggestions? #git#config#versioncontrol#linux@gitea
@5am have you looked at chezmoi? https://chezmoi.io
I initially thought about using a setup similar to yours, but after reading the docs, I gave up on reinventing the wheel.
Chezmoi makes it incredibly easy to get all your configuration files into version control and if you need to manage differences between systems, it's got you covered as well.
I have a set of configs I need for work, some stuff I only need at home and a few things that are specific to Windows. 🙂
@5am I use @gitea (self hosted) and keep all my #k8s (k3s, actually) and whatnot in different projects. I use #1password’s op command to inject secrets into the various #yaml files. I use just to automate common tasks. It all works great.
@alto@gitea Fair enough. I use GitLab for anything that's public / non-sensitive, and it's great. I just feel more comfortable hosting sensitive stuff locally where it's behind a firewall and not exposed.
@alto@gitea No, I don't believe I would be able to self-host the email service I use, even if it was an option, nor would I want to due to the complex nature (as I understand it) of hosting and securing your own mail server to the same standards as the better providers out there. My email is end-to-end encrypted and I trust the provider. The way I see it is you have to trust some providers. It's just about choosing them carefully.
@alto@5am@gitea I think Email is very different than Git in this regard. Once your email leaves your home server, self-hosted or otherwise, you have no control over what happens to it. So there’s little value in hosting your own Email server IMO.
Add comment