Re-bootstrap data container in a split setup?

Product Support

AI-generated summary

A user, calmh, is running a split setup with separate data and web-only containers for Discourse. The containers are currently running on different versions, and calmh wants to update the data container without causing downtime or data loss.

riking suggests stopping the web container, rebuilding the data container, and then restarting the web container using the command ./launcher stop web && ./launcher rebuild data && ./launcher start web.

After trying the suggested command, calmh reports no adverse effects. sam confirms that the correct steps are to stop the web container, rebuild the data container, and then rebuild the web container.

1

I’m running a split setup (data and web_only containers). This makes it easy and quick to update the web container with minimal downtime. :+1:

However, I noticed today that the web container I’m running is based on samsaffron/discourse 1.0.10 while the data container is based on samsaffron/discourse 1.0.6. Presumably, at some point, it would be a good idea to update the data container as well.

What’s the recommended process there? Shut down the web container, destroy, bootstrap and launch a new data container, then launch the web container again? Are there any gotchas related to the update, in terms of not screwing up my data…?

2

If that’s correct, which it seems to be, that would be:

./launcher stop web && ./launcher rebuild data && ./launcher start web
3

Is this correct @sam?

4

The recipe above seems to have done it’s thing with no adverse effects.

5

Yes that is correct,

stop web
rebuild data
rebuild web