# Zelf-gehoste upgrade naar 3.1.0.beta2 met typische multi-container installatie vereist extra downtime

**URL:** https://meta.discourse.org/t/self-hosted-upgrade-to-3-1-0-beta2-with-typical-multi-container-install-requires-extra-downtime/252916
**Category:** Self-hosting
**Created:** [25 januari 2023 om 20:31 UTC](https://meta.discourse.org/t/self-hosted-upgrade-to-3-1-0-beta2-with-typical-multi-container-install-requires-extra-downtime/252916 "2023-01-25T20:31:40Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)
#### Post date: [26 januari 2023 om 02:48 UTC](https://meta.discourse.org/t/self-hosted-upgrade-to-3-1-0-beta2-with-typical-multi-container-install-requires-extra-downtime/252916/17 "2023-01-26T02:48:04Z")

</div>

I had seen the `SKIP_POST_DEPLOYMENT_MIGRATIONS` doc. What I had _really_ missed was this post that shows how to do zero downtime deployments with `launcher`:

> [@Zero Downtime Upgrades](https://meta.discourse.org/t/zero-downtime-upgrades/120673/2):
>
> We successfully performed the upgrade a couple of months ago. I’m posting our experience here for anyone who may have the same question in the future. Discourse somewhat supports zero downtime upgrades by using [post deployment migrations](https://meta.discourse.org/t/introducing-post-deployment-migration/98974). The overall process, as we understood it, can be divided in 2 steps. STEP 1: Upgrade to the new version and run safe migrations: Update all your plugins and themes to be compatible with the new version. (This is actually quite a bit of work depending on you…

So now I have to think about that, now that I know that it is feasible. If I do it, I’ll update [MKJ's Opinionated Discourse Deployment Configuration](https://meta.discourse.org/t/mkjs-opinionated-discourse-deployment-configuration/193355) with what I do.

I’ve been having lots of trouble getting worked up about it when I am providing four, some months four and a half nines of availability on a service that I run for free in my spare time. It’s a testament to the quality of Discourse development that I can do that on a tests-passed policy, including things like the extra minute or so of downtime I saw this time, and sometimes rebooting the host for security updates.

---

_[View the full topic](https://meta.discourse.org/t/self-hosted-upgrade-to-3-1-0-beta2-with-typical-multi-container-install-requires-extra-downtime/252916)._