Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rethink how configuration is stored and pushed to servers #91

Open
rahulbot opened this issue Dec 28, 2018 · 0 comments
Open

rethink how configuration is stored and pushed to servers #91

rahulbot opened this issue Dec 28, 2018 · 0 comments
Assignees

Comments

@rahulbot
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants