The Twelve-Factor app manifesto calls for strict separation of configuration from code. This approach provides several advantages:
- Sensitive values such as API tokens and private keys will not be leaked if the codebase was ever exposed.
- There is no need for a switch statement for each environment defining various variables for dev, staging, etc..
- Feature toggles can be used to dynamically enable functionality without a deployment.
Configuration management is very simple on Skpr, available directly from
Deleting a configuration key/value pair can be done using the configuration delete documentation.
Listing configuration can be done using the Configuration listing documentation.
Setting configuration can be done using the Configuration setting documentation.
skpr config --help usage: skpr config <command> [<args> ...] Config operations Flags: --help Show context-sensitive help (also try --help-long and --help-man). Subcommands: config get <environment> <key> Get a single config value for the specified environment. config list <environment> List all of the config key/value pairs for the specified environment. config set [<flags>] <environment> <key> [<value>] Set a config value for the specified environment. config delete [<flags>] <environment> <key> Deletes a config value for the specified environment.