From ed9a8e6830e3fd93f6071379dda982843e7d107c Mon Sep 17 00:00:00 2001 From: CodeYourDay Date: Mon, 11 Sep 2017 14:09:37 +0200 Subject: [PATCH] Update Typo fix -> servers.json is deprecated --- 2.0/docs/configs/config.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/2.0/docs/configs/config.md b/2.0/docs/configs/config.md index 9cb389e0..e5e0ca3e 100644 --- a/2.0/docs/configs/config.md +++ b/2.0/docs/configs/config.md @@ -76,18 +76,18 @@ let mongoUrl = drop.config["keys", "mongo", "url"]?.string ?? "default" ## Advanced Configurations -Having the default `servers.json` is great, but what about more complex scenarios. For example, what if we want a different host in production and in development? These complex scenarios can be achieved by adding additional folders to our `Config/` directory. Here's an example of a folder structure that's setup for production and development environments. +Having the default `server.json` is great, but what about more complex scenarios. For example, what if we want a different host in production and in development? These complex scenarios can be achieved by adding additional folders to our `Config/` directory. Here's an example of a folder structure that's setup for production and development environments. ```bash WorkingDirectory/ ├── Config/ -│ ├── servers.json +│ ├── server.json │ ├── production/ -│ │ └── servers.json +│ │ └── server.json │ ├── development/ -│ │ └── servers.json +│ │ └── server.json │ └── secrets/ -│ └── servers.json +│ └── server.json ``` > You can specify the environment through the command line by using --env=. Custom environments are also available, a few are provided by default: production, development, and testing.