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

[Drupal] Split staging from production environment & feature / version lock #102

Open
4 tasks
AnthonyAstige opened this issue Jun 28, 2016 · 0 comments
Open
4 tasks
Assignees
Milestone

Comments

@AnthonyAstige
Copy link
Member

Hey Lowell,

Sorry I couldn't make it today. Aaron mentioned we're planning to launch very soon. It feels like now is a good time to setup a separate staging environment from production, so that you can work on/demo stuff and not worry about breaking the real website.

TODO

  • Setup staging environment
  • Make an easy way (single script?) to copy configuration from staging to production
  • Mental note to only work on bug fixes / stability in the master branch as we're going into launch
  • Hand this someone on the front end (Levi or me) to sync up the [Consumer] dev side to use the staging environment's data
@AnthonyAstige AnthonyAstige added this to the MVP milestone Jun 28, 2016
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

No branches or pull requests

2 participants