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

Single Deploy Settings #155

Merged
merged 4 commits into from
May 7, 2015
Merged

Single Deploy Settings #155

merged 4 commits into from
May 7, 2015

Conversation

mlavin
Copy link
Contributor

@mlavin mlavin commented Apr 17, 2015

Fixes #102. All environments use a single live settings and configure changes via environment variables. The current is pass to allow if blocks (an example is included for Vagrant). Also related to #103 but there are still a few places like the fabfile which hard code the staging/production expectation. Hoping to address that when adding GPG secrets support. That will make added a new environment pretty straight forward: one new pillar file and minimal fab task to set master IP, environment name.

Hopefully this will also clear up the confusion about how to use Vagrant. Vagrant, like all other environments, use the production requirements and settings. It's not perfect but it's a start. Feedback welcome.

@dpoirier
Copy link
Contributor

To me it's not immediately obvious what the word "live" means in this context. I wonder if we changed that to "deployed"? It's intended for anything not running locally using runserver, right?

@mlavin
Copy link
Contributor Author

mlavin commented Apr 22, 2015

Not the greatest name. Didn't want to name it for an environment like prod because it will be used for all environments. Maybe deploy or deployed. Vagrant will use these settings as well. Do you think that will cause confusion?

@mlavin
Copy link
Contributor Author

mlavin commented Apr 23, 2015

@vkurup gave another vote for deploy so I'll make that update.

@mlavin
Copy link
Contributor Author

mlavin commented May 4, 2015

Any outstanding objections before merging this?

@dpoirier
Copy link
Contributor

dpoirier commented May 5, 2015

👍 from me.

mlavin added a commit that referenced this pull request May 7, 2015
@mlavin mlavin merged commit a31d711 into master May 7, 2015
@mlavin mlavin deleted the deploy-settings branch May 7, 2015 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

proposal: re-organize settings inheritance for staging & production
2 participants