Vagrantfile in discourse_docker repo - for production?

AI-generated summary

The discussion centers on the purpose and future of the Vagrantfile in the discourse_docker repo. pihentagy asks whether the Vagrantfile is intended for production use and how to access the Discourse instance inside it (default IP: 192.168.33.11), or if it should be used as a template. Falco clarifies that it was never meant for production — it was originally for Docker file development, and since no maintainers use it anymore, it will be deleted. He directs users to the Discourse official Standard Installation for production setups. chandan.gupta shares that they’ve been using the Vagrantfile locally on macOS to test Docker image builds (up to 2.5.0.beta4) with custom templates and app.yml, and relied on it to validate builds before deployment. After upgrading to 2.5.0.beta7, they found the Vagrantfile removed and now lack a local way to run the launcher script. Falco responds that building Discourse Docker images locally on macOS requires a virtualized Linux environment, since the Vagrant setup was unmaintained and prone to bit rot. Both development and automated builds now occur in Linux environments, and no official alternative for macOS is provided.

Is the https://github.com/discourse/discourse_docker/blob/master/Vagrantfile file supposed to be used for production?

If yes, how one can reach the discourse installation inside? (by default it maps to 192.168.33.11)

Or should I just copy it and use it as a template?

No it is not. It was originally used for development of the Docker files. As no maintainer uses it anymore I will delete it. Thanks for the heads up.

For running Discourse in production please follow Discourse official Standard Installation.

I have been using the vagrantfile to test the discourse docker image build on my mac until 2.5.0.beta4. We have some custom templates, custom app.yml, etc. Testing image build via the launcher script helps confirm that nothing is broken before deploying it. Our pipeline doesn’t need vagrant, but locally I don’t know any other way of running the launcher script other than the vagrant vm. After upgrading to 2.5.0.beta7, I realized that vagrantfile is removed, so I can’t build the discourse image locally any more.

What is your recommendation on building the discourse docker image locally on a mac?

You will need a virtualized linux environment for that. As said above no maintainers used the vagrant setup so it was prone to bit rot and not something we could support. Currently both development and automated builds of the image happen in a Linux environment.