Conversation

Notices

1. Embed this notice
   FoolishOwl (foolishowl@social.coop)'s status on Wednesday, 19-Feb-2025 04:05:42 JST FoolishOwl

   Would it be a good idea to initialize a git repository in a directory for config files when deploying a new service?

   I'm working on learning more about git, and this struck me as a possible application, but I can't remember anyone suggesting it specifically.

   • Embed this notice
     Håkan Geijer (hakan_geijer@kolektiva.social)'s status on Wednesday, 19-Feb-2025 04:05:41 JST Håkan Geijer

     in reply to

     @foolishowl I feel like you just need to use ansible so the version history is local

   • Embed this notice
     Anarcho Doggo (anarchodoggo@kolektiva.social)'s status on Wednesday, 19-Feb-2025 04:16:35 JST Anarcho Doggo

     in reply to

     • Håkan Geijer

     @hakan_geijer yeah I wish ansible was faster but it's great for this scenario. @foolishowl
     and you can use "ansible vault" to encrypt a lot of the stuff you obv don't want in plaintext in git. So when you provision it uses the vault key to decrypt on the fly and you can commit the encrypted version in git. Definitely a useful way to handle sensitive config file info (I put even ssh pubkeys in this category). Makes stuff like firewall setup, web server config, user management, ssh hardening / config, etc nicely abstracted and readily reproducible.

     The other configuration management tools (chef, puppet, etc) have major drawbacks and a lot more complexity, so +1 to learning ansible for this