# Container deployment rework
**URL:** https://meta.discourse.org/t/container-deployment-rework/98108
**Category:** Development
**Created:** [September 26, 2018, 12:44pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108 "2018-09-26T12:44:38Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@rowanj](https://meta.discourse.org/u/rowanj)
#### Post date: [September 26, 2018, 12:44pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108/1 "2018-09-26T12:44:38Z")
Would Team Discourse be open to some fairly significant rework of the `discourse_docker` and any other setup and launch scripts to bring the install experience (and documentation, of course) more in-line with Docker expectations and philosophy?
Specifically:
- Clear course to deploy the application with existing redis/postgres infrastructure
- `sudo`-less generation of application config
- explicit resource targets
… and other issues as they arise
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [September 26, 2018, 12:58pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108/2 "2018-09-26T12:58:51Z")
It is unlikely you could accomplish this without breaking many many things but you are welcome to try.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [September 26, 2018, 12:59pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108/3 "2018-09-26T12:59:30Z")
@rowanj you may be interested in the previous discussion here:
> [@Can Discourse ship frequent Docker images that do not need to be bootstrapped?](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205):
>
> There is this [open issue](https://github.com/discourse/discourse_docker/issues/186) (which I just closed) on Discourse Docker repo asking Discourse should behave like a standard docker image a docker user excepts to be able to run discourse without a special launcher. to define multiple containers (redis, postgres, discourse,..), links and volumes, docker-compose should be used instead. [Docker Compose | Docker Docs](https://docs.docker.com/compose/) The question is somewhat misguided, but I would like to address a broader one of Can Discourse ship frequent Docker images that do …
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 26, 2018, 1:34pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108/4 "2018-09-26T13:34:43Z")
Providing a docker image with a fixed set of plugins that could be configured only with environment variables isn’t that hard.
But supporting a bunch of people to use it would be untenable.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 26, 2018, 2:59pm UTC](https://meta.discourse.org/t/container-deployment-rework/98108/5 "2018-09-26T14:59:51Z")
> [@rowanj](#):
>
> Clear course to deploy the application with existing redis/postgres infrastructure
This is supported out of the box, remove the templates from PostgreSQL / Redis and set the correct environment variables in the `app.yml`.