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
Since the Dockerfiles have distinct configurations and requirements between launcher and deployment environments, we will implement separate Docker configurations for each environment. This separation will help maintain cleaner version control by preventing merge conflicts that often arise when different teams work on environment-specific Docker settings. By maintaining dedicated configurations for each environment, we can ensure better organization of our Docker setup and allow for independent evolution of launcher and deployment specifications without interference.
cont.
we also need to clear up the env var confusion between prod vars and local vars. we can either split .env.example into .env.prod.example & .env.local.example , OR we keep the same .env.example and just add clear details to the viewer, i.e.
### PROD ###
a=...b=...c=...
### LOCAL ###
a=...b=...c=...d=...e=...
Can we remove the re-declaring of a, b & c and add a comment saying “local needs all above (prod) vars, along with the following..."
Currently it is hard for devops to look at the .env.examples to know which vars are actually necessary for deployments, and which ones are only necessary for running repos locally.
The text was updated successfully, but these errors were encountered:
Since the Dockerfiles have distinct configurations and requirements between launcher and deployment environments, we will implement separate Docker configurations for each environment. This separation will help maintain cleaner version control by preventing merge conflicts that often arise when different teams work on environment-specific Docker settings. By maintaining dedicated configurations for each environment, we can ensure better organization of our Docker setup and allow for independent evolution of launcher and deployment specifications without interference.
cont.
we also need to clear up the env var confusion between prod vars and local vars. we can either split
.env.example
into.env.prod.example
&.env.local.example
, OR we keep the same.env.example
and just add clear details to the viewer, i.e.Currently it is hard for devops to look at the .env.examples to know which vars are actually necessary for deployments, and which ones are only necessary for running repos locally.
The text was updated successfully, but these errors were encountered: