leveraging docker-compose(or npm) to setup environment variables and using them to write environment specific code. For example :- using google analytics, build scripts only in 'production' environment.
At present, to make redirection to HTTPS only on development-notes.quantecon and notes.quantecon and not on localhost, environment variable is set on Dockerfile-server, as we are not using docker for localhost. If we intend to use docker in our local environments in future, or if we want to have separate environment variables for development server and production server, we will have to create multiple docker-compose files.
It will a good practise anyways to make environment specific docker-compose files.
leveraging docker-compose(or npm) to setup environment variables and using them to write environment specific code. For example :- using google analytics, build scripts only in 'production' environment.
At present, to make redirection to HTTPS only on development-notes.quantecon and notes.quantecon and not on localhost, environment variable is set on Dockerfile-server, as we are not using docker for localhost. If we intend to use docker in our local environments in future, or if we want to have separate environment variables for development server and production server, we will have to create multiple docker-compose files. It will a good practise anyways to make environment specific docker-compose files.