---
updatedAt: 2026-10-02T09:42:09.000Z
agentTools:
  siteIndex: https://techdocs.akamai.com/llms.txt
  projectIndex: https://techdocs.akamai.com/quick-deploy-apps/llms.txt
---

# Discourse

Deploy [Discourse](https://www.discourse.org/), a self-hosted, open source discussion platform that provides a forum, mailing list, chat room, and more.

## Set up SMTP before deployment

Discourse requires that you have access to a personal SMTP (Simple Mail Transfer Protocol) server before installation.

This requires either having access to a pre-existing SMTP server or setting up an SMTP relay service through a third party, like [Bird](https://bird.com/en-us/products/email/sparkpost), [Twilio](https://www.twilio.com/en-us/sendgrid), [Mailjet](https://www.mailjet.com/), [Mailgun](https://www.mailgun.com/), or another provider. Linode doesn't offer an SMTP relay service at this time.

You need an SMTP username and password for a server under your control to complete the installation.

Additionally, the SMTP user must be able to send email from `noreply@your-domain.com` for administrator account verification.

* For example, if you enter a subdomain of discourse and your domain name is `example.com`, then the SMTP user must be able to send email from `noreply@discourse.example.com`.
* You aren't required to use a subdomain. Therefore, if you only set up `example.com` without a subdomain, the email used for verification would be `noreply@example.com`.

See also our [guides](https://www.akamai.com/cloud/guides/email) for details on configuring an email server on a Linode.

> 🚧 Email restrictions on Akamai Cloud
>
> Outbound connections on ports 25, 465, and 587 are blocked by default on Linode instances for some new accounts to help reduce spam originating from our platform. These restrictions prevent applications from sending email. If you intend to send email from a Linode instance, review the [Send email on Akamai Cloud](https://techdocs.akamai.com/cloud-computing/docs/send-email) guide to learn more about our email policies and to request the removal of these restrictions.

## 1. Deploy Discourse

<div class="aligned">
   <img src="https://techdocs.akamai.com/terraform-images/img/clock.png" alt="" height="25" width="25" />
   <span class="span-header">&nbsp;Estimated deployment time:</span><span>&nbsp;15–20 minutes</span>
</div>

<div><p></p></div>

Follow the [deployment instructions](https://techdocs.akamai.com/quick-deploy-apps/docs/get-started) from the **Get started** section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the [Configuration options](#configuration-options) section.

### Software included

Software installed on your Linode when deploying the app.

| Package       | Description                         |
| ------------- | ----------------------------------- |
| **Discourse** | An open source discussion platform. |
| **Docker**    | A container management runtime.     |

### Base distribution and plan

* **Supported distribution:** Ubuntu 24.04 LTS
* **Recommended plans:** 4GB Shared Compute Instance

### Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (`stackscript_data`) required for automated deployments.

**StackScript ID:** `688891`

<table>
    <thead>
        <tr>
            <th>UI field</th>
            <th>API/CLI key</th>
            <th>Description</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td colspan="3">Required options</td>
        </tr>
        <tr>
            <td><b>Limited sudo user</b></td>
            <td><code>user_name</code></td>
            <td>Your preferred username for the limited sudo user, entered without any capital letters, spaces, or special characters.<br /> When adding a limited sudo user, the account is assigned to the <code>sudo</code> group, which provides elevated permissions when running commands with the <code>sudo</code> prefix.
                <blockquote>
                    <b>Note:</b> For easier and more secure access with the sudo user, add an <a href="https://techdocs.akamai.com/cloud-computing/docs/manage-ssh-keys">account SSH key</a> for the Cloud Manager user during deployment and select that user as an <code>authorized_user</code>. Their SSH pubkey will be assigned to both the root and limited sudo users.
                </blockquote>
            </td>
        </tr>
        <tr>
            <td><b>Admin email address</b></td>
            <td><code>discourse_admin_email</code></td>
            <td>The Dicourse admin email address.</td>
        </tr>
        <tr>
            <td><b>Admin username</b></td>
            <td><code>discourse_admin_username</code></td>
            <td>The admin username used to log in to Discourse.</td>
        </tr>
        <tr>
            <td><b>SMTP server address</b></td>
            <td><code>smtp_address</code></td>
            <td>The address for the Simple Mail Transfer Protocol (SMTP). Discourse uses this for sending emails.</td>
        </tr>
        <tr>
            <td><b>SMTP username</b></td>
            <td><code>smtp_user_name</code></td>
            <td>The username for the SMTP account. The SMTP user must be able to send emails from <a>noreply@your-fully-qualified-domain.com</a> for account verification.</td>
        </tr>
        <tr>
            <td><b>SMTP password</b></td>
            <td><code>smtp_password</code></td>
            <td>The password for the SMTP account.</td>
        </tr>
        <tr>
            <td><b>Dicourse notification email</b></td>
            <td><code>smtp_notification_email</code></td>
            <td>The Dicourse notification email.</td>
        </tr>
        <tr>
            <td colspan="3">Advanced options</td>
        </tr>
        <tr>
            <td><b>Disable root access over SSH</b></td>
            <td><code>disable_root</code></td>
            <td><i>Applies to a limited sudo user.</i> To block the root user from logging in over SSH, select <i>Yes</i>. Defaults to <i>No</i>. <br />
                <blockquote>
                    <b>Note:</b> When you disable the root user from logging in over SSH and don't provide a valid Account SSH Key assigned to the <code>authorized_user</code>, you can still switch to the root user. To do that, log in as root via the <a href="https://techdocs.akamai.com/cloud-computing/docs/access-your-system-console-using-lish">Lish console</a> and run <code>cat /home/$USERNAME/.credentials</code> to view the generated password for the limited sudo user.
                </blockquote>
            </td>
        </tr>
        <tr>
            <td><b>Linode API token</b></td>
            <td><code>token_password</code></td>
            <td><i>Applies to a custom domain.</i> The Linode API token if you want to use Linode's <a href="https://techdocs.akamai.com/cloud-computing/docs/dns-manager">DNS Manager</a> to manage DNS records for your custom domain. Follow <a href="https://techdocs.akamai.com/cloud-computing/docs/manage-personal-access-tokens">Manage personal access tokens</a> to get your token on your account with <code>Read/Write</code> access to <code>Domains</code>.
                <ul>
                    <li>If you provide the token along with the subdomain and domain, the installation attempts to create DNS records via the Linode API.</li>
                    <li>If you don't provide the token, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.</li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><b>Subdomain</b></td>
            <td><code>subdomain</code></td>
            <td><i>Applies to a custom domain.</i> The subdomain you want to use, like <code>blog</code> for <code>blog.example.com</code>. Requires a <i>Linode API token</i>.</td>
        </tr>
        <tr>
            <td><b>Domain</b></td>
            <td><code>domain</code></td>
            <td><i>Applies to a custom domain.</i> The domain name you want to use, like <code>example.com</code>. Requires a <i>Linode API token</i>.</td>
        </tr>
        <tr>
            <td><b>SMTP port</b></td>
            <td><code>smtp_port</code></td>
            <td>The SMTP port used to send mail. Defaults to <i>587</i>.</td>
        </tr>
        <tr>
            <td><b>Optional data exporter Add-ons</b></td>
            <td><code>add_ons</code></td>
            <td>An option to include add-ons for your deployment. Possible values are:
                <ul>
                    <li><i>none</i> (default)</li>
                    <li><i>node_exporter</i></li>
                    <li><i>mysqld_exporter</i></li>
                    <li><i>newrelic</i></li>
                </ul>
            </td>
        </tr>
    </tbody>
</table>

> **Notes:**
>
> * After the app deployment completes, the password for your limited sudo user is generated and stored in the `.credentials` file in the home directory, along with application-specific passwords. Log in to your instance as `root` through the [Lish console](https://techdocs.akamai.com/cloud-computing/docs/access-your-system-console-using-lish) or [SSH](https://techdocs.akamai.com/cloud-computing/docs/set-up-and-secure-a-compute-instance#connect-to-the-linode), then run `cat /home/$USERNAME/.credentials` to view its contents.
> * You can automatically configure a **custom domain** (optional) during deployment. To do that:
>   1. First, configure your domain to use Linode’s name servers via your registrar. See [Configure your domain's authoritative name servers](https://techdocs.akamai.com/cloud-computing/docs/configure-your-domains-authoritative-name-servers) for details.
>   2. Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.

### Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and [app-specific fields](#configuration-options) along with the standard Linode deployment configurations.

> **Note:** [Generate a personal access token](https://techdocs.akamai.com/linode-api/reference/get-started#personal-access-tokens) to authenticate your [API](https://techdocs.akamai.com/linode-api/reference/api), [CLI](https://techdocs.akamai.com/cloud-computing/docs/cli-1), or [Terraform](https://registry.terraform.io/providers/linode/linode/latest/docs) requests.

```bash API
curl --location 'https://api.linode.com/v4/linode/instances' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer abc123def456hij789klm' \
    --data-raw '{
        "region": "us-east",
        "type": "g6-standard-2",
        "image": "linode/ubuntu24.04",
        "label": "my-discourse-one-click-app",
        "root_pass": "@C0mpl3x#P@ssw0rd",
        "stackscript_id": 688891,
        "stackscript_data": {
            "user_name": "jsmith",
            "discourse_admin_email": "admin@example.com",
            "discourse_admin_username": "admin",
            "smtp_address": "smtp.example.com",
            "smtp_user_name": "smtp-jsmith",
            "smtp_password": "P@ssw0rd1234",
            "smtp_notification_email": "noreply@example.com"
        }
    }'
```
```bash CLI
linode-cli linodes create \
    --region us-east \
    --type g6-standard-2 \
    --label my-discourse-one-click-app \
    --image linode/ubuntu24.04 \
    --root_pass @C0mpl3x#P@ssw0rd \
    --stackscript_id 688891 \
    --stackscript_data '{"user_name":"jsmith", "discourse_admin_email":"admin@example.com", "discourse_admin_username":"admin", "smtp_address":"smtp.example.com", "smtp_user_name":"smtp-jsmith", "smtp_password":"P@ssw0rd1234", "smtp_notification_email":"noreply@example.com"}'
```
```json Terraform
resource "linode_instance" "my-linode" {
    region         = "us-east"
    type           = "g6-standard-2"
    label          = "my-discourse-one-click-app"
    image          = "linode/ubuntu24.04"
    root_pass      = "@C0mpl3x#P@ssw0rd"
    stackscript_id = 688891
    stackscript_data = {
        "user_name"                = "jsmith"
        "discourse_admin_email"    = "admin@example.com"
        "discourse_admin_username" = "admin"
        "smtp_address"             = "smtp.example.com"
        "smtp_user_name"           = "smtp-jsmith"
        "smtp_password"            = "P@ssw0rd1234"
        "smtp_notification_email"  = "noreply@example.com"
    }
}
```

## 2. Access Discourse

Once the app is deployed, you can start using Discourse. To do that:

1. Navigate to the Discourse app in your browser with the fully qualified domain name you entered during configuration. For example, `https://subdomain.your-domain.com` or `https://your-domain.com`.
2. Discourse then launches the main discussion listing page where you can start adding discussion topics.

## Additional resources

For more information about the installed packages, see their official documentation.

* [Discourse Get Started Tutorials](https://blog.discourse.org/tag/getting-started/)
* [Discourse on GitHub](https://github.com/discourse/discourse)
* [Discourse Community](https://meta.discourse.org/)

> 📘
>
> Note that we can't vouch for the accuracy or timeliness of externally hosted resources.

# Sibling pages

* [Ant Media Server - Community Edition](https://techdocs.akamai.com/quick-deploy-apps/docs/ant-media-community-edition.md)
* [Ant Media Server - Enterprise Edition](https://techdocs.akamai.com/quick-deploy-apps/docs/ant-media-enterprise-edition.md)
* [AzuraCast](https://techdocs.akamai.com/quick-deploy-apps/docs/azuracast.md)
* [Jitsi](https://techdocs.akamai.com/quick-deploy-apps/docs/jitsi.md)
* [Jitsi (cluster)](https://techdocs.akamai.com/quick-deploy-apps/docs/jitsi-cluster.md)
* [LiveSwitch](https://techdocs.akamai.com/quick-deploy-apps/docs/liveswitch.md)
* [Mastodon](https://techdocs.akamai.com/quick-deploy-apps/docs/mastodon.md)
* [Owncast](https://techdocs.akamai.com/quick-deploy-apps/docs/owncast.md)
* [Plex Media Server](https://techdocs.akamai.com/quick-deploy-apps/docs/plex-media-server.md)