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

<div class="post-metadata">

**Author:** ![ShawnLi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shawnli/32/280402_2.png) [@ShawnLi](https://meta.discourse.org/u/ShawnLi)\
**Post date:** [November 5, 2022, 5:31am UTC](https://meta.discourse.org/t/migrate-quickly-to-separate-web-and-data-containers/153355/23 "2022-11-05T05:31:18Z")

</div>

Hi, mcdanlj! I am new here. I find that discourse has two deployment methods, one is the standalone mode of app.yml, the other is your method which is to split the database and redis cache into multicontainer mode of web-only.yml, data.yml, redis.yml. But at the same time, I also find that app.yml can also be connected to redis and database by modifying the parameters DISCOURSE\_DB\_HOST and DISCOURSE\_REDIS\_HOST, so why do we need to split the app.yml into web-only.yml, data.yml and redis.yml?

---

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