# Migrate quickly to separate web and data containers

**URL:** https://meta.discourse.org/t/migrate-quickly-to-separate-web-and-data-containers/153355
**Category:** Sysadmins
**Tags:** migrations, how-to, advanced-setup
**Created:** [May 31, 2020, 12:55am UTC](https://meta.discourse.org/t/migrate-quickly-to-separate-web-and-data-containers/153355 "2020-05-31T00:55:48Z")
**Posts on this page:** 1
**Showing post:** 28

<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: [November 5, 2022, 8:01pm UTC](https://meta.discourse.org/t/migrate-quickly-to-separate-web-and-data-containers/153355/28 "2022-11-05T20:01:46Z")

</div>

@ShawnLi If the two-container system seems complicated, that’s a good sign that the one-container default is a good choice for you. The two-container deployment saves a few minutes of downtime about once per month while updating, but does require more understanding, and requires that you manually follow the details in the announcements every new release.

That’s why I led with:

> [@mcdanlj](#):
>
> If you read the instructions below and it feels like magic, rather than clarifying how things actually work inside the containers, _run, don’t walk_ to your nearest default **standalone** deployment and you’ll do yourself a favor.

😀

---

_[View the full topic](https://meta.discourse.org/t/migrate-quickly-to-separate-web-and-data-containers/153355)._
