# 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:** 13

<div class="post-metadata">

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

</div>

> [@mcdanlj](#):
>
> the old software still running fails due to a schema inconsistency

Are you doing a two-stage migration with [Introducing Post Deployment Migration](https://meta.discourse.org/t/introducing-post-deployment-migration/98974) ?

This pattern is critical if you’re doing e.g. a blue/green deployment and need the previous version to continue to function.

---

_[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)._