rowanj
(Rowan James)
Setembro 26, 2018, 12:44pm
1
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
It is unlikely you could accomplish this without breaking many many things but you are welcome to try.
david
(David Taylor)
Setembro 26, 2018, 12:59pm
3
@rowanj you may be interested in the previous discussion here:
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 overview | Docker Docs
The question is somewhat misguided, but I would like to address a broader one of
Can Discourse ship frequent Docker images …
pfaffman
(Jay Pfaffman)
Setembro 26, 2018, 1:34pm
4
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
(Falco)
Setembro 26, 2018, 2:59pm
5
This is supported out of the box, remove the templates from PostgreSQL / Redis and set the correct environment variables in the app.yml.