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
The current approach creates high friction when we have multiple deploy environments:
you have maintain to have a local checkout and/or branch for each server
pulling in from master to your deploy branch/checkout is annoying
double-checking to make sure you aren't pushing config to the wrong server/github is stressful and risky
I suggest switching to a file-or-env approach like python-dotenv. This would let you have all the config set up as environment variables in the container, and each person would maintain their own local config file that is loaded into env when you run your local server.
The text was updated successfully, but these errors were encountered:
The current approach creates high friction when we have multiple deploy environments:
I suggest switching to a file-or-env approach like python-dotenv. This would let you have all the config set up as environment variables in the container, and each person would maintain their own local config file that is loaded into env when you run your local server.
The text was updated successfully, but these errors were encountered: