# Zero Downtime Upgrades

**URL:** <https://meta.discourse.org/t/zero-downtime-upgrades/120673>\
**Category:** Development\
**Created:** [18.Июнь.2019 13:53:55 UTC](https://meta.discourse.org/t/zero-downtime-upgrades/120673 "2019-06-18T13:53:55Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Eduardo\_Poleo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eduardo_poleo/32/155764_2.png) [@Eduardo\_Poleo](https://meta.discourse.org/u/Eduardo_Poleo)\
**Post date:** [18.Июнь.2019 13:53:55 UTC](https://meta.discourse.org/t/zero-downtime-upgrades/120673/1 "2019-06-18T13:53:55Z")

</div>

Hello there,

We are wondering if zero downtime upgrades are possible. We are using the discourse\_docker installation using separate web and data containers, so the issue is more around the old application code (v2.1) running against a migrated v2.3.0 database schema. This happens between the time we bootstrap the image (which will run the migrations) and the moment the web servers get restarted (updated) to run the upgraded image. Are there any recommendation for this?

---

_[View the full topic](https://meta.discourse.org/t/zero-downtime-upgrades/120673)._
