Timeline for How do I keep my production site online when doing deployments?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2016 at 19:55 | comment | added | Chris Berg | That's the piece I was missing - aseabridge's answer suggests multiple publishing targets - giving each CD its own database. | |
| Oct 7, 2016 at 18:33 | comment | added | Alan Płócieniak | How do you want do it if you have code-to-content dependency? You cannot update content first as both instances uses the same db and publicly exposed instance might return errors with new content. And the same with code, without new content it will not work. No, I didn't automate that because I needed clone only few times. Of course we are talking about the worst case scenario, normally I do it without cloning because changes are not critical, so I only disconnect instance from LB, install update package and done. | |
| Oct 7, 2016 at 13:33 | comment | added | Chris Berg | Cloning databases seems unnecessarily complicated... Were you able to automate this? | |
| Oct 6, 2016 at 20:41 | history | edited | Alan Płócieniak | CC BY-SA 3.0 |
added 130 characters in body
|
| Oct 6, 2016 at 20:35 | history | answered | Alan Płócieniak | CC BY-SA 3.0 |