Add env config changes to docs

Author: andreievg

build/mac/open_msupply_server.sh

@@ -10,4 +10,4 @@ cd "$(dirname "$0")"
 chmod +x bin/remote_server
 xattr -cr bin/remote_server
 $(sleep 3 && open "http://localhost:8000") &
-APP_SERVER__DANGER_ALLOW_HTTP=true ./bin/remote_server
+APP__SERVER__DANGER_ALLOW_HTTP=true ./bin/remote_server

server/README.md

@@ -110,7 +110,7 @@ From version 2.0 omSupply would require both legacy and omSupply central server
 - `cargo run` twice but change port, database and sync settings in yaml file or overwrite with env variables
 
 For example, two sites running locally from the same repo,  __central__ and  __test__, for __central__ site `Site is open mSupply central server` is checked and `This site url` is http://localhost:2055. 
-Comment out all sync settings in yaml and can start  __central__ with `APP_SERVER__PORT=2055 APP_DATABASE__DATABASE_NAME="central_test" cargo run` front end would be started with `yarn start -- -- --env API_HOST='http://localhost:2055' --port 3005` (--port is for webpack port), and then start  __test__ with `cargo run` and `yarn && yarn start-local` from respective folders. The first site would be initialised with `central` site credentials first, and second sites with  __test__ credentials,  __test__ site would sync with both legacy mSupply and omSupply central server (this  __central__ site), and __central__ site would synchronise with legacy mSupply server only
+Comment out all sync settings in yaml and can start  __central__ with `APP__SERVER__PORT=2055 APP__DATABASE__DATABASE_NAME="central_test" cargo run` front end would be started with `yarn start -- -- --env API_HOST='http://localhost:2055' --port 3005` (--port is for webpack port), and then start  __test__ with `cargo run` and `yarn && yarn start-local` from respective folders. The first site would be initialised with `central` site credentials first, and second sites with  __test__ credentials,  __test__ site would sync with both legacy mSupply and omSupply central server (this  __central__ site), and __central__ site would synchronise with legacy mSupply server only
 
 
 ### Start server in watch mode
@@ -211,13 +211,13 @@ If you want to ensure all your changes have been written to the main sqlite data
 
 `note`: yaml configurations are likely to be deprecated to .env, thus documentations is limited for .yaml.
 
-In `configurations` folder you'll find `.yaml` config files, there is `base`, `local` (will overwrite/expand `base` in dev mode), `production` (will overwrite/expand other configs when `APP_ENVIRONMENT=production ).
+In `configurations` folder you'll find `.yaml` config files, there is `base`, `local` (will overwrite/expand `base` in dev mode), `production` (will overwrite/expand other configs when `APP__ENVIRONMENT=production ).
 
-You can use env variable to overwrite any configurations, can use dot notation with `__` (two underscore) to specify nested value. Env vars configuration overrides start with `APP_`.
+You can use env variable to overwrite any configurations, can use dot notation with `__` (two underscore) to specify nested value. Env vars configuration overrides start with `APP__`.
 
 ```bash
 # example, will overwrite sync.url config in yaml
-APP_SYNC__URL='http://localhost:8001' cargo run
+APP__SYNC__URL='http://localhost:8001' cargo run
 ```
 
 ## Export initialisation

server/server/src/configuration.rs

@@ -85,7 +85,7 @@ pub fn get_example_file_path(configuration_directory: PathBuf) -> PathBuf {
 /// For example, the following runs the application using the `local` configuration with the
 /// `database.port` value set to `5433`:
 ///
-/// APP_ENVIRONMENT=local APP_DATABASE__PORT=5433 cargo run
+/// APP__ENVIRONMENT=local APP__DATABASE__PORT=5433 cargo run
 ///
 pub fn get_configuration_environment() -> Environment {
     Environment::with_prefix(CONFIGURATION_ENVIRONMENT_PREFIX)

server/service/src/sync/test/integration/README.md

@@ -45,14 +45,14 @@ Only data that needs to be present on central server site is a new sync site (th
 ## 4 `Open mSupply central server`
 
 - Another instance of omSupply should be running as central server, in order to set omSupply instance as central server, you will need to check "Site is open mSupply central server" against the site and enter correct This site url agains the site in mSupply->Special->Synchronisation->{Site}
-- And graphql API should be 'open' (without token), thus 'APP_SERVER\_\_DEBUG_NO_ACCESS_CONTROL' env variable should be set to `true`
+- And graphql API should be 'open' (without token), thus 'APP__SERVER\_\_DEBUG_NO_ACCESS_CONTROL' env variable should be set to `true`
 
 In case you are wondering, the APP env variables translate to settings in [configuration .yaml](https://github.com/msupply-foundation/open-msupply/blob/1b8b9237863eef1a764be3973d563e6d84358827/server/configuration/example.yaml#L7) files, and override them
 
 Here is the full command line I used, for this setting "test" site `Site is open mSupply central server` is ticked and `This site url` is set to "http://localhost:2055"
 
 ```bash
-APP_SERVER__PORT=2055 APP_DATABASE__DATABASE_NAME="central_test" APP_SYNC__URL="http://localhost:2048" APP_SYNC__INTERVAL_SECONDS=30 APP_SERVER__DEBUG_NO_ACCESS_CONTROL=TRUE APP_SYNC__PASSWORD_SHA256="d74ff0ee8da3b9806b18c877dbf29bbde50b5bd8e4dad7a3a725000feb82e8f1" APP_SYNC__USERNAME="test" cargo run
+APP__SERVER__PORT=2055 APP__DATABASE__DATABASE_NAME="central_test" APP__SYNC__URL="http://localhost:2048" APP__SYNC__INTERVAL_SECONDS=30 APP__SERVER__DEBUG_NO_ACCESS_CONTROL=TRUE APP__SYNC__PASSWORD_SHA256="d74ff0ee8da3b9806b18c877dbf29bbde50b5bd8e4dad7a3a725000feb82e8f1" APP__SYNC__USERNAME="test" cargo run
 ```
 
 In this case d74ff0ee8da3b9806b18c877dbf29bbde50b5bd8e4dad7a3a725000feb82e8f1 = pass