Hello everyone! :blush: I hope you’re all doing well! I have a question about Discourse: Is it possible to self-host Discourse? I’m really interested in the platform and would love to know if anyone here has experience with it. Are there any specific requirements or tips I should keep in mind? Thank you in advance for your help! :folded_hands:

Yes, and there’s an entire Subcategory dedicated to it!: #self-hosting You would want to specifically read standard install

Thank you very much for your answers! I would like to have a standalone ‘docker-compose’ file that I can launch and use discourse in our association Is that possible? I’m not a fan of running a thousand scripts in the background that I don’t know

Yes it’s possible but you’d need to write and support it yourself. Here’s a Dockerfile someone posted recently for development that might act as a starter [image] Dockerfile (Apple/M1) for launching Discourse stable branch (v3.3.3) in 2025 Development Hi there! Some days ago I started learning Discourse and didn’t find a Dockerfile for Apple/M chips. So I had created my own and I would like to share it with anyone who also wants keep a control over own image. Also by this post I would like to learn how Discourse and community work. I hope you find my post helpful. You are welcome to provide any feedback/thoughts/questions about my Dockerfile. My Dockerfile is for Apple/M chips, but can be easily modified # https://meta.discourse.org/t/ins… [image] Max Hammer: I’m not a fan of running a thousand scripts in the background that I don’t know Discourse is open source. Why not read the launcher scripts and templates? (which would also inform your Compose)

This is unsupported, but there are efforts trying to keep up with mainline Discourse. You can search for docker compose here, or visit these two variants: Install Discourse using Docker and Docker Compose discourse · main · indiehost / libre.sh / Images · GitLab Careful though, maintaining Discourse across versions can prove difficult. But IndieHosters have been doing it for some years now. Both projects use the original Discourse/base docker image but I’m not sure they’re tailoring the installation like @sam’s pups does for discourse-docker.

Thx for you’re replies! I’ve installed only the discourse/base image but the container exited with no logs [The image shows a command-line interface displaying a container named "discourse-container" in a Docker environment, which was recently exited with no processes running.] Does you know why?

Because the base image does nothing by itself. You need to compile Discourse in it and then run it. And that is done by executing a ./launcher script outside of the image first. So you should first try to install it the official way and then think about the options. The Discourse installation procedure is not very common but over the years I really like the approach for one reason, which you will only appreciate after being an admin for some time. And that is the possibility to upgrade it after each commit to the source code. It’s incredible. You report a #bug, after 1 hour it may very well be addressed by the team or the community, the automatical tests are executed and the commit is merged and available. And you can upgrade straight away. Because you recompile your Discourse on the latest source code. So there is no image where any specific version would be compiled. You get an “empty” image and compile your version from the point you want and with the combination of plugins you need. And it still works! You don’t get this kind of flexibility anywhere else. So I am not sure, but if you want to make a docker compose file, you will need to replicate the ./launcher script procedure inside the compose file, so you compile it to another image, which you can then just plug in. But you cannot use the built-in procedure when you need an upgrade. You will have to go and compose a new version by yourself.

Thanks for your help guys. You make it easy for beginners like me to use Discourse! Yes, but before I make Discourse available to my club, I wanted to run Discourse on the localhost and do some tests so that I can get along better with the admin interface and the command line of Discourse. If errors occur, I want to be able to fix them. For the ‘supported’ version I need a DNS entry, port 443 and 80 which is unnecessary in my case - at least I think so. Does anyone know a hack on how to run this on the localhost?

[image] Robert: You would want to specifically read standard install Install Docker and just do this.

[image] Max Hammer: Does anyone know a hack on how to run this on the localhost? Yes: https://meta.discourse.org/tags/c/documentation/developer-guides/56/dev-install :slight_smile:

Or that. Although I understood that Max is interested in getting to know how it behaves in production but to test it locally before purchasing a hosting environment. For that the docker setup would be more appropriate. In order to actually fix bugs, the dev setup is the right choice.

Discourse Self Hosting with Docker compose

Product Support Self-hosting

Canapin (Coin-coin le Canapin) January 26, 2025, 6:00pm 11

Yes:

https://meta.discourse.org/tags/c/documentation/developer-guides/56/dev-install

Topic		Replies	Views
Docker-compose.yml to run discourse locally Self-hosting unsupported-install	3	7458	July 18, 2023
Install with Docker compose Self-hosting docker	7	16063	July 11, 2018
Docker compose addition Self-hosting hosting	1	286	March 3, 2026
Is Docker image discourse/discourse considered safe and production-ready? Self-hosting hosting	30	3714	May 26, 2026
How to install Discourse locally? Self-hosting	13	17133	July 12, 2022

Discourse Self Hosting with Docker compose

Related topics