# Benefits of running discourse in separate containers for data and web

**URL:** https://meta.discourse.org/t/benefits-of-running-discourse-in-separate-containers-for-data-and-web/36109
**Category:** Self-hosting
**Tags:** docker, hosting
**Created:** [2015年十一月28日 12:08 UTC](https://meta.discourse.org/t/benefits-of-running-discourse-in-separate-containers-for-data-and-web/36109 "2015-11-28T12:08:30Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Yuun](https://avatars.discourse-cdn.com/v4/letter/y/977dab/32.png) [@Yuun](https://meta.discourse.org/u/Yuun)
#### Post date: [2015年十一月28日 16:08 UTC](https://meta.discourse.org/t/benefits-of-running-discourse-in-separate-containers-for-data-and-web/36109/4 "2015-11-28T16:08:23Z")

</div>

Per [https://meta.discourse.org/t/advanced-troubleshooting-with-docker/15927](https://meta.discourse.org/t/advanced-troubleshooting-with-docker/15927), the database is actually stored outside the container(s).

AFAIK the main advantage of separating containers (if you’re changing nothing else about the default install) is reducing downtime when you’re running `./launcher rebuild app`. However it’s a bit outside my knowledge and not something I’ve attempted doing, so I wouldn’t be surprised if there were more reasons to do it.

---

_[View the full topic](https://meta.discourse.org/t/benefits-of-running-discourse-in-separate-containers-for-data-and-web/36109)._