# Bootstrap app container in 2 steps

**URL:** <https://meta.discourse.org/t/bootstrap-app-container-in-2-steps/116865>\
**Category:** Feature\
**Created:** [May 4, 2019, 9:36pm UTC](https://meta.discourse.org/t/bootstrap-app-container-in-2-steps/116865 "2019-05-04T21:36:48Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**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:** [January 2, 2020, 7:27pm UTC](https://meta.discourse.org/t/bootstrap-app-container-in-2-steps/116865/5 "2020-01-02T19:27:43Z")

</div>

> [@lucasbasquerotto](#):
>
> perhaps this feature would increase the complexity of the project, but I think very little

As someone who spends an insane amount of time supporting novice sysadmins, I think it increases the complexity very much. It takes an enormous amount of work to support just the one dead-simple foolproof configuration. Even managing a two-container install and knowing to do replace `app` with `web_only` (not to mention knowing how and when to update the data container) increases the complexity at least 4 fold.

> [@lucasbasquerotto](#):
>
> To use **the same base image in staging and production** to avoid problems caused by different commits in the discourse repository or in the plugins directory when updating discourse

This, I think is the big win.

---

_[View the full topic](https://meta.discourse.org/t/bootstrap-app-container-in-2-steps/116865)._