From 7d49a760fa42a7c2ed646667c6de4ee16b31b76d Mon Sep 17 00:00:00 2001 From: Hunter Long Date: Fri, 6 Jul 2018 11:45:23 -0700 Subject: [PATCH] Updated Config with .env File (markdown) --- Config-with-.env-File.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Config-with-.env-File.md b/Config-with-.env-File.md index 00b16e0..4ae8246 100644 --- a/Config-with-.env-File.md +++ b/Config-with-.env-File.md @@ -1,6 +1,6 @@ It may be useful to load your environment using a `.env` file in the root directory of your Statup server. The .env file will be automatically loaded on startup and will overwrite all values you have in config.yml. -If you have the `DB_CONN` environment variable set Statup will bypass all values in config.yml and will require you to have the other DB_* variables in place. +If you have the `DB_CONN` environment variable set Statup will bypass all values in config.yml and will require you to have the other DB_* variables in place. You can pass in these environment variables without requiring a .env file. ## `.env` File ```bash