2 ms·
The idea of versioned configuration is in part a result of gui-driven configuration. If you can configure via text file, then configuration can be versioned via
by beat 9y ago
The idea of versioned configuration is in part a result of gui-driven configuration. If you can configure via text file, then configuration can be versioned via standard version control mechanisms. Otherwise, you're going to wind up with something half-assed.
I had a lot of insight when I started using Concourse CI. All CI workflows in Concourse are straight-up yaml files - no gui anything. This is such a different experience from almost entirely gui-driven systems like Jenkins.
- madsohm 9y agoIf your SaaS already have an export option for the configuration, it shouldn't be that hard to versionize it as well. You could intercept all database calls that change the configuration and just save a copy of the current one. This can be done in many ORMs already.