I followed the guide at discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub to install Discourse, and it felt pretty straight-forward. However, I’m now building an automated install to fit into our other deploy patterns and suddenly it doesn’t feel so simple anymore.
When installing/running gitea, jenkins or any of a number of other apps we run in docker we write a
docker-compose.yml file and simply run
docker-compose up. Trying that pattern with Discourse feels difficult.
Instead I have to clone the git repo, deploy my app.yml to it (instead of running the setup, which doesn’t lend itself to automation), and run the launcher… What exactly does the launcher do? And which files from the repo are needed, and for what?
An adjacent question regarding the instance I have running: I update it through the web GUI, but what would happen if I run
git pull in
/var/discourse and rebuild the app, without making sure I’ve upgraded it inside the docker container?