Discourse Cloud Install Checklist: Server, Domain, and Setup
Deploying a self-hosted forum can seem complex, but the official installation tools streamline the process onto standard cloud servers. As detailed in the official Discourse cloud install guide, administrators can set up Discourse in about 10 minutes without requiring background knowledge of Rails or Linux shell scripting. Use this checklist to verify your server sizing, address setup, email options, and post-installation security steps.
1. Server Hardware and OS Requirements Checklist
Before launching your virtual server, confirm that the host environment satisfies the baseline operational requirements. If you are evaluating multiple platforms for your community, review our comparison of forum software server requirements for context on different forum engines.
- Operating System: A 64-bit Linux distribution is required, with Ubuntu LTS recommended.
- System Memory: A minimum of 1 GB RAM (which requires swap) is needed, while 2 GB or more is recommended. The installer automatically offers swap creation on low-memory machines.
- Processing Power: At least 1 CPU core is required; 2 or more cores are recommended.
- Disk Capacity: 10 GB of storage space is the minimum requirement, with 20 GB or more recommended.
- Port Availability: Confirm that ports 80 and 443 are not already in use by competing web services such as Nginx or Apache.
- Hosting Provider: Compatible with any cloud provider supporting Docker and root SSH access, including DigitalOcean, AWS EC2, Google Cloud Platform, Linode / Akamai, Vultr, and Hetzner.
2. Domain Name and DNS Routing Checklist
Discourse requires a valid web address during installation to provision automatic SSL certificates via Let's Encrypt. Choose one of two domain routes before executing the setup script:
- Free Subdomain Option: Claim a free subdomain ending in yoursite.discourse.diy at id.discourse.com/my/subdomain. Generate a 6-digit verification code, which remains valid for 10 minutes. The installer uses this code to automatically create a DNS A record pointing to your server's public IP address, bypassing manual DNS editing.
- Custom Domain Option: Buy a domain from a registrar such as Namecheap. In your registrar or DNS management dashboard, create a DNS A record directing your chosen subdomain (such as forum.example.com) to your server's IP address. Note that DNS propagation can take up to 48 hours.
3. Email and Authentication Strategy Checklist
Historically, forum setup required active outgoing mail servers immediately. Under current setup rules, SMTP configuration is completely optional at install time:
- Skip SMTP (Discourse ID): Choosing to skip email setup enables Login via Discourse ID. Members sign in using social logins (Google, Facebook, Apple, and GitHub) or through id.discourse.com. Web push notifications still reach users across browsers and Progressive Web App (PWA) devices without a mail provider.
- Configure SMTP: If your community depends on mailing list mode, replying via email, or periodic digest emails, enter your SMTP provider details during the installation wizard or add them later via Admin → Email.
4. Installation and Wizard Execution Checklist
Once your server is provisioned and your address option is ready, proceed through the server build steps outlined in the Discourse cloud installation documentation:
- Access Server: Connect to your remote machine over SSH as the root user.
- Run Single-Command Installer: Execute the command
wget -qO- https://raw.githubusercontent.com/discourse/discourse_docker/main/install-discourse | sudo bash. The script automatically installs Docker and git if they are not present. - Input Configuration: Provide the email addresses intended for administrator accounts, select whether you are using a free subdomain or a custom domain, and choose whether to configure or skip SMTP.
- Wait for Automated Build: The wizard checks ports 80 and 443, detects the public IP, auto-tunes UNICORN_WORKERS and db_shared_buffers based on server RAM and CPU, and builds the application in roughly 5 to 10 minutes.
5. Post-Installation Verification and Security Checklist
After the build finishes, confirm access and apply system-level safeguards. For additional server-hardening best practices, consult our guide to protecting your forum from takeovers.
- Register the Admin Account: Navigate to your forum URL via HTTPS, select Sign Up or Log In, and register using one of the exact admin email addresses specified during installation.
- Complete In-App Setup: Walk through the introductory in-app wizard to establish forum defaults.
- Automate System Updates: Enable unattended package updates on your Ubuntu or Debian host using
dpkg-reconfigure -plow unattended-upgrades. - Prevent Brute-Force Logins: Install fail2ban on the host system via
apt install fail2ban. - Maintenance Routine: Keep Discourse up to date using the web updater at /admin/upgrade or via the command line in /var/discourse with
./launcher rebuild app. You can also purge stopped containers older than 24 hours with the launcher cleanup command.
Sources
Published October 28, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.