Self-hosting Discourse gives full control but needs setup

Running Discourse on your own infrastructure means you own every byte of data, from user posts to plugin configurations. The trade‑off is that the initial setup demands attention to a few specific steps; skipping any of them can leave the forum unable to send notifications or accept logins.
The Discourse project describes itself as a 100 % open‑source community platform that has been battle‑tested for over a decade. It offers real‑time chat, theme customization, and a plugin system that includes AI‑powered chatbots. If you prefer to avoid managing servers, the official hosting service handles updates, backups, and scaling for you. The pricing page (https://discourse.org/pricing) outlines the tiers for that managed option.
When you decide to self‑host, the typical workflow begins with pulling the official Discourse Docker image. After the container starts, the setup wizard guides you through hostname selection, database configuration, and admin account creation. At this point the platform will boot and you can reach the login screen. However, the wizard does not automatically configure outbound email. If you leave the SMTP settings blank, Discourse will log errors such as “Could not connect to SMTP host” whenever it tries to send a welcome message or a password‑reset link.
The next step, therefore, is to edit the app.yml file (or the environment variables if you use a compose file) and add valid SMTP credentials. You need to specify the host, port, username, password, and optionally enable TLS. After saving the file, you must rebuild the container with ./launcher rebuild app. Once the rebuild finishes, test the configuration by triggering a notification from the admin panel; a successful delivery confirms that the mail pipeline works.
If you skip the SMTP configuration, the forum will still allow users to browse and post, but they will not receive email confirmations, which can lead to confusion during registration and hinder password recovery. Re‑building the container after correcting the mail settings resolves the issue without affecting existing data.
Choosing between self‑hosting and the official service hinges on how much control you want versus operational overhead. Self‑hosting gives you the freedom to install custom plugins, tweak theme assets, and enforce any data‑retention policy you need, but you must monitor Docker logs, keep the image updated, and maintain the mail server. The managed option removes those chores, letting you focus on community growth while Discourse handles the underlying stack.
Either path provides access to the same core features: real‑time chat, theme marketplace, and the Discourse AI plugin for automated assistance. Verify your installation by checking the version number displayed in the admin dashboard; it should match the latest stable release tagged on the project’s repository. With the mail service correctly configured, your Discourse instance will be ready to support meaningful conversations without interruption.