I use discourse alongside a proxy, since i have other services on my server, and use ./launcher to install discourse, would i be able to install in the same with this new method?
If you already have Discourse installed on your server, this doesn’t apply to you. This new installer is for new installs on servers that will only run Discourse, the most common use case.
Really pleased to see this development, great work!
Will this work for a Raspberry Pi?
Has anyone tried?
This is so cool!!!
IIRC Raspberry Pis can already host Discourse:
Ian - I see a couple others clarified that you can still configure email support and enable mailing list mode for a forum created this way. But I’m not sure that’s what you’re asking.
It sounds like you feel a forum that doesn’t offer mailing list mode should somehow warn users of that fact when they go to register. But forum operators already had the choice to enable or disable mailing list mode:

So that’s not a new result of this updated setup process.
Is an official Helm Chart also coming up for Kubernetes?
I get that but interested in the install method for a new server whereas I run a web panel already.
It works on any Linux server with internet access, so it definitely works.
However, if you are running it on your home internet without the ability to listen on the usual ports, you will want to follow Install Discourse on a residential internet with Cloudflare Tunnel to work around that.
This new guide is focused on making our “Get Started” story better, even for non-technical users. It’s optimized for signing up for a € 3 server and having Discourse running in 10 minutes.
We have @featheredtoast working on solving the Can Discourse ship frequent Docker images that do not need to be bootstrapped? problem, which when shipped could then lead to a Helm chart.
As said above, this is for enabling people to buy a cheap VPS and get started as soon as possible.
Advanced configurations with custom reverse proxies are still possible as they always have been, but when you choose to walk outside the beaten path, you also sign up for spending more time on the downfall of the chosen complexity.
As an update on this, we have images up on docker hub today, all self hosted sites I’m hosting are using it without issue, but moving recommendations over requires updating the docs and the scripts surrounding that all.
It also hinges on updating parts of our hosting and making sure everything there is rock solid before recommending it for general release. Parts are moving and the last few pieces should be in place soon™
Just read the announcement, sounds like incredible news!!
Wow! That’s very cool. I guess I can think about retiring my elaborate Ansible scripts that build images with launcher. . .
Yes, you’re right, that was my meaning. I didn’t know that ML mode was optional. And now that I think of it, it probably doesn’t make sense to somehow treat this one aspect of diverse Discourse communities specially; there are many other ways in which a new community can prove unfamiliar and difficult to use for someone who already follows a number of them. So, maybe this should be a more general feature: have a link on the sign up page to a quick summary of the global settings. I have a feature request now!
If this had been available earlier, I wouldn’t have spent so much time studying configuration files.
Why
This new installer, the optional SMTP and the free .discourse.diy subdomains when paired with Bundling more popular plugins with Discourse core means that for most new instances, the admins will never need to dabble into the YAML ![]()
Just wanted to say huge thanks to the team for doing this. I love the thoughtfulness of Discourse’s design features and I’ve been wanting to self host for years but it was a little too complex to tackle even with experience installing other stuff. And thanks @Canapin for posting the screenshots of the install process, that was extremely helpful.
6 posts were split to a new topic: Discourse ID setup issues on Hetzner