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

Refresh Development Database with Production Database #118

Open
onelittlebecca opened this issue Jun 28, 2015 · 4 comments
Open

Refresh Development Database with Production Database #118

onelittlebecca opened this issue Jun 28, 2015 · 4 comments
Assignees

Comments

@onelittlebecca
Copy link

Please clone the production database to the dev database so we can effectively test the MySchedule and BoF features of COD. :-)

@onelittlebecca
Copy link
Author

Please include @Nneka and me on how to do this (and hell, even some of the other stuff) so that we can help. Acquia's dev environment is weird.

I should add, we both know we can and have copied databases down from prod to dev in normal situations and environments but we don't want to mess anything up and we recognize that acquia's dev environment is different from reg dev environments we have worked in before.

@dsheffler
Copy link

Hey now...it's not that bad. :)

Sent from my iPhone

On Jun 28, 2015, at 1:53 PM, Becca [email protected] wrote:

Please include @Nneka and me on how to do this (and hell, even some of the other stuff) so that we can help. Acquia's dev environment is weird.


Reply to this email directly or view it on GitHub.

@timwood
Copy link
Contributor

timwood commented Jul 9, 2015

@onelittlebecca To do this, just log into the Acquia cloud web interface and drag/drop the DB and files from Prod to Dev. Since we don't have any automated hooks to scrub user's password/email, when testing functionality, make sure you don't end up emailing everyone on the site!

@timwood
Copy link
Contributor

timwood commented Jul 9, 2015

Also a good idea to create a backup of any environments involved.

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

3 participants