Tim Cooke wrote:... configuration stored in the code repo and that is packaged up into the build artefact. There are many reasons why this is not ideal
Tim Cooke wrote:A Wiki page?
Tim Cooke wrote:Let's say that the database user credentials change, oh shoot now we need to build, test, and deploy a new version of the application. This is sub optimal.
“Code becomes a build, which is combined with config to create a release.”
From: Wiggins, Adam. “The Twelve-Factor App.”
12factor.net wrote:The twelve-factor app stores config in environment variables (often shortened to env vars or env). Env vars are easy to change between deploys without changing any code; unlike config files, there is little chance of them being checked into the code repo accidentally; and unlike custom config files, or other config mechanisms such as Java System Properties, they are a language- and OS-agnostic standard.
Eliminate 95% of the weeds in your lawn by mowing 3 inches or higher. Then plant tiny ads:
how do I do my own kindle-like thing - without amazonhttps://coderanch.com/t/711421/engineering/kindle-amazon