Version control of configuration without secrets

Hi team,

thank you for a great job!

I want to have all my configs in a public git repo. In the example of SWAG I’m struggling to separate the secrets from the config itself. E.g to check in cert.key to a public git is not a good idea.

  • Are config volumes intended to be in a git repo?
  • What is the backup and rollback strategy then?


There is no intent on our part. if you backup /config you can restore everything. If you make no custom changes, you really don’t need to backup swag.

backup strategies and rollback strategies are for you to develop, test, and implement to suit your environment.