From 1cf9fad0360d4b563a4dd58ef6983e48f452d203 Mon Sep 17 00:00:00 2001 From: Jan-Erik Rediger Date: Fri, 4 Mar 2016 12:31:59 +0100 Subject: [PATCH] fix: Correct filename --- ...mdv => 2016-03-04-load-your-config-into-your-environment.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename _posts/{2016-03-04-load-your-config-into-your-environment.mdv => 2016-03-04-load-your-config-into-your-environment.md} (96%) diff --git a/_posts/2016-03-04-load-your-config-into-your-environment.mdv b/_posts/2016-03-04-load-your-config-into-your-environment.md similarity index 96% rename from _posts/2016-03-04-load-your-config-into-your-environment.mdv rename to _posts/2016-03-04-load-your-config-into-your-environment.md index f156b70..5ca7d14 100644 --- a/_posts/2016-03-04-load-your-config-into-your-environment.mdv +++ b/_posts/2016-03-04-load-your-config-into-your-environment.md @@ -5,7 +5,7 @@ date: 04.03.2016 12:30 --- It became quite popular to store certain configuration variables in your environment, to be later loaded by your aplication. -This way of [having all configuration](config) available is part of the [twelve-factor app definition][12factor]. +This way of [having all configuration][config] available is part of the [twelve-factor app definition][12factor]. The idea is to place your variables in a `.env` file and load this as environment variables to be accessed by your application. Most of the time you can just plug in one of the dozens of libraries that load this config from a file and your application can fetch the values as normal from the environment.