But what about migrations? Do they respect upgrades between new releases? How do you manage to solve the case when new release makes breaking changes in db?

Can you explain you question, keeping in mind that each rebuild will run db:migrate

If one of the docker container makes breaking changes in db how do they share the same db in production?

I still do not understand your question, slowly, can you explain clearly what you are asking for … and first read this: templates/web.template.yml master filename: "/etc/nginx/conf.d/discourse.conf" from: /client_max_body_size.+$/ to: client…

[Bild] Manually update Discourse and Docker image to latest If you want zero downtime, you must run 2 web containers and cycle them in and out using haproxy So, one container in public and the second one is on stage. Let’s imagine that the second one goes with migration which makes breaking ch…

As far as I understand you, both of the containers will share the same db. Am I right?

breaking db changes will always cause downtime we can not magic that away

It’s possible by making them responsible for old code and some kind of convention, imho.

Otherwise, people have to observe migrations that you have done.

I have no idea what you are proposing here and am having extreme issues following you. IF we decide one day to rename the table topics to amazing-topics then old web servers running our old repo will break. Only way to keep them working under such conditions is to create a writable view during the …

[Bild] sam: Only way to keep them working under such conditions is to create a writable view during the migration that keeps backwards compat in place. In general our migrations are backwards compat. Rarely they are not, when they are not there is a minor outage. This is exactly what I’m tal…

Can you upgrade Discourse seamlessly if there is a breaking db change?

Support

skyeagle 3. April 2015 um 21:22 5

So, one container in public and the second one is on stage. Let’s imagine that the second one goes with migration which makes breaking changes in db (for example, removes column). How do the first one will react on this?

Thema		Antworten	Aufrufe
How do I upgrade Discourse in a multiple container configuration? Self-hosting	2	965	8. Oktober 2020
Upgrade without rebuilding having a good/ready image? Support	5	204	13. Dezember 2025
Zero Downtime Upgrades Development	1	2173	11. September 2019
Is it by design that updates via web UI can provoke breaking changes? Support	3	226	3. Januar 2025
Help with "zero downtime" setup Self-hosting hosting	7	2400	10. September 2020

Can you upgrade Discourse seamlessly if there is a breaking db change?

Verwandte Themen