I’ve read both pages in detail, as well as a ton of other information. Just a couple of points I’ll make:
- In a production HA environment, it is not acceptable to have a single container run Rail,Redis, Postgresql, and Nginx.
- It’s not clear to me if the current Discourse Docker solution will run properly on an existing Docker Cluster with many other containers already running
- Our environment already has HA Postgresql, Redis, and a Docker Cluster - These should be leveraged
- The Discourse rails app should have the ability to start with a ‘docker stack deploy’ function, not a ./launcher script.
I’ve run many rails containers before for enterprise applications. What I’m looking for is to understand if I’m going to need to build my own Discourse container (I hope not). And if not, where can I get the Discourse container (preferably from a ‘docker pull’ command) and start it with ‘docker stack deploy’ with a matching docker-compose.yml file.
I also need to know exactly what folders and files from inside the container I need to mount to the host (all our persistent data runs from a very fast NFS mount).
So, to recap, I intend to have a docker-compose.yml file that contains all the information to start the Discourse Rails app, including mounts, and the ability to scale replicas.