Container deployment rework

[rowanj (Rowan James)]

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

[codinghorror (Jeff Atwood)]

It is unlikely you could accomplish this without breaking many many things but you are welcome to try.

[david (David Taylor)]

@rowanj you may be interested in the previous discussion here:

Can Discourse ship frequent Docker images that do not need to be bootstrapped?

There is this open issue (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 Documentation The question is somewhat misguided, but I would like to address a broader one of Can Discourse ship frequent Docker images …

[pfaffman (Jay Pfaffman)]

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.

[Falco (Rafael dos Santos Silva)]

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.