You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.
With recent changes to the 1.7 deployment we have started to use a .env file for some, but not all variables required for a docker based deployment. We should consider the maintenance impact of choosing one or the other or a mixture of both. We should also discuss how to make the current files consistent with any decision made as well, e.g. open a single issue to convert all parameters, or work iteratively when there is an opportunity.
ross-spencer
changed the title
Issue: Discuss parameters for including settings in .env vs. docker-compose.yml
Problem: Discuss parameters for including settings in .env vs. docker-compose.yml
Jun 12, 2018
With recent changes to the 1.7 deployment we have started to use a
.env
file for some, but not all variables required for a docker based deployment. We should consider the maintenance impact of choosing one or the other or a mixture of both. We should also discuss how to make the current files consistent with any decision made as well, e.g. open a single issue to convert all parameters, or work iteratively when there is an opportunity.The files we're configuring options in are:
The text was updated successfully, but these errors were encountered: