Timeline for Best Practices for Acquia: Reconciling Production Database back to Dev before update; what is the workflow?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2018 at 22:46 | comment | added | Kevin | It really just depends. I had to patch some contributed modules that other projects didn’t have. It all varies. | |
| Apr 27, 2018 at 22:43 | comment | added | Jordan W. | Hey @Kevin, I definitely do not intend to do it all in prod. I have 3 envs, dev-staging-prod, in my Acquia setup. I was more or less wondering if it really should be as difficult and broken as it has been in my dry-runs so far. When I pull prod to dev, start running db updates, module updates, and entity updates, everything breaks...like a lot. I guess I should just expect that, was what I was after. Thanks! | |
| Apr 27, 2018 at 22:34 | comment | added | Kevin | ^ that whole method, when you have it down, shouldn't take any longer than 2 minutes to complete deploying it to prod. You can alternatively attempt to update production with your steps, but if you are worried about breaking the site, do it the other way. Take plenty of database backups. | |
| Apr 27, 2018 at 22:33 | comment | added | Kevin | I don't know what you can expect. It depends on what you are using. But definitely don't do it all in prod.. thats what I provided the shortcut. Take a prod db snapshot and try the upgrade locally, debug it, write down the steps/patches/whatever.. do some dry runs.. then when you are ready, put the site in maintenance mode, take a prod db snapshot, apply the updates, then RESTORE production with that database and deploy the code. That way you're not risking breaking production. I did this for one of the 12 projects I manage because I had to mitigate some modules with patches and test it out. | |
| Apr 27, 2018 at 22:28 | comment | added | Jordan W. | @Kevin I should expect heavy debugging, right? So far, in my tests leading up to now, even just updating prod from 8.4.3 to 8.4.8 or 8.5.1 breaks....everything, it seems like. | |
| Apr 27, 2018 at 21:13 | comment | added | Kevin | One way to do it is copy prod database down, set the site to maintenance mode and request no admins be in the site. Get the database updated, then copy that back to prod with the new code. That way you don’t have to run updates on prod. I’ve done that. I took a fairy big update that took five hours to perform and test, then doing it for real only seemed like 5 seconds of downtime. | |
| Apr 27, 2018 at 21:04 | answer | added | Arakwar | timeline score: 0 | |
| Apr 27, 2018 at 17:38 | comment | added | Jordan W. | Why are you people down-voting my post instead of trying to be helpful? Ridiculous. | |
| Apr 27, 2018 at 11:51 | history | asked | Jordan W. | CC BY-SA 3.0 |