# Passage du conteneur autonome à des conteneurs web et données séparés **URL:** \ **Category:** Sysadmins\ **Tags:** docker, how-to, advanced-setup, two-container\ **Created:** [Mai 29, 2015, 2:12 UTC](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413 "2015-05-29T14:12:22Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [Juillet 4, 2017, 5:32 UTC](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413/9 "2017-07-04T17:32:27Z")
> [@tophee](#): > > In other words: what’s the catch? For people like you and me, there is none. When the 30 minute install was conceived, it involved editing `app.yml` with a tool like nano (I’m an Emacs user and even I prefer `vi` to nano). Having people edit copy and edit _two_ files and bootstrap and start both of them in the right order is on the order of 10 times more complicated. Now that `./discourse-setup` is how most people configure Discourse, the setup part could be exactly the same for a two-container setup. I’ve looked in to doing just that & it wouldn’t be very hard. But even still, with two containers, there would then be a bunch of problems with the data container wasn’t running and then no one would say which way their site was configured and that would be a lot more complicated to help out. Most of the time the web-based upgrade works just fine, and so unless you’re changing your plugin config, there’s not _that_ much of a win for the two-container setup. I think soon that I’ll start offering a two-container setup along side of my [$99 install](https://www.literatecomputing.com/product/discourse-install/), but I’ve not gotten around to it. --- _[View the full topic](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413)._