How do you manage multiple environments? about express-typescript-boilerplate

[dweber019]

Hi @et

Yes just setup a .env file for your local environment.
You should not have multiple config files on one environment. In addition you should not commit any sensitive data to a repository (e.g. DB user and password).

In my opinion a other party needs to provide configuration. For example if you use cloud services like Cloud Foundry or Heroku (https://devcenter.heroku.com/articles/heroku-postgresql#connecting-in-node-js) you will load this configuration from the environment variables and this configuration is provided by the cloud provider.

What we do on Cloud Foundry is to setup a manifest.yaml to hold the more static env vars.

And if you have a CI like Travis or Jenkins you would also provide the config over the environment variables.

If you like to add an other environment or change the configuration of an environment you don't have to change the version control. You just have to change the config in the cloud and restart the app.

Thanks for the link to convict. Seams like an awesome library perfect for frontend (E.g. Webpack webapp) configuration (as there the configuration has to be loaded on at build/compile time).

[et]

Thanks for response. Env vars are the way to go. Totally forgot that dotenv doesn't overwrite existing env vars so that should be a safe path.
Thanks!