# Help with "zero downtime" setup

**URL:** <https://meta.discourse.org/t/help-with-zero-downtime-setup/163668>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [September 10, 2020, 7:44pm UTC](https://meta.discourse.org/t/help-with-zero-downtime-setup/163668 "2020-09-10T19:44:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![LSD2020](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lsd2020/32/165673_2.png) [@LSD2020](https://meta.discourse.org/u/LSD2020)\
**Post date:** [September 10, 2020, 7:58pm UTC](https://meta.discourse.org/t/help-with-zero-downtime-setup/163668/3 "2020-09-10T19:58:16Z")

</div>

I think this makes sense. So the data container does not run a rebuild via launcher? I would just handle load balancing via the host level Nginx. Let me see if I can sort this:

data container:

```plaintext
./launcher enter data_container 
SKIP_POST_DEPLOYMENT_MIGRATIONS=1 rake db:migrate

```

web\_container

```plaintext
./launcher rebuild web_container1 && \
sleep 60 && ./launcher rebuild web_container2 

```

data container:

```plaintext
rails generate post_migration
SKIP_POST_DEPLOYMENT_MIGRATIONS=0 rake db:migrate

```

Does that seem sane?

---

_[View the full topic](https://meta.discourse.org/t/help-with-zero-downtime-setup/163668)._
