linode · hmorris3293 · Mar 23, 2026 · Mar 30, 2026
diff --git a/docs/marketplace-docs/guides/apache-airflow/index.md b/docs/marketplace-docs/guides/apache-airflow/index.md
@@ -2,6 +2,7 @@
 title: "Deploying Apache Airflow"
 description: "Deploy Apache Airflow on a Linode Compute Instance. This provides you with an open-source workflow management platform for data engineering pipelines."
 published: 2023-01-23
+modified: 2026-03-30
 keywords: ['airflow','workflow management','data engineering']
 tags: ["quick deploy apps", "linode platform", "cloud manager"]
 external_resources:
@@ -32,7 +33,7 @@ To learn more about Airflow and determine if it's the right tool for you, read t
 
 ## Configuration Options
 
-- **Supported distributions:** Ubuntu 20.04 LTS
+- **Supported distributions:** Ubuntu 24.04 LTS
 - **Recommended plan:** All plan types and sizes can be used.
 
 ### Apache Airflow Options
@@ -45,45 +46,41 @@ To learn more about Airflow and determine if it's the right tool for you, read t
 
 {{% content "marketplace-special-character-limitations-shortguide" %}}
 
-## Getting Started after Deployment
+### Obtain the Credentials
 
-1. Log into your new Compute Instance through [LISH](/docs/products/compute/compute-instances/guides/lish/) or [SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) using the root user and the password you entered when creating the instance.
+Once the app is deployed, you need to obtain the credentials from the server:
 
-1. If you log in on the same day you deployed the app, a message is displayed with a link to your Apache Airflow GUI and the username and password to use.
+1. Log in to your new Compute Instance using one of the methods below:
 
-    ```output
-    The installation of Apache Airflow is now complete, and the application is running in standalone mode.
-    #
-    You can log into the Airflow GUI at 192-0-2-170.ip.linodeusercontent.com
-    With the credentials:
-    Username: admin
-    Password: pNbgWNDhYcRNvgRq
-    #
-    Standalone mode is not recommended for production.
-    ```
+    - **Lish Console**: Log in to Cloud Manager, click the **Linodes** link in the left menu, and select the Compute Instance you just deployed. Click **Launch LISH Console**. Log in as the `root` user. To learn more, see [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/).
+    - **SSH**: Log in to your Compute Instance over SSH using the `root` user. To learn how, see [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/).
 
-    If you don't see this message, you can output it using the command below:
+2. Run the following command to access the contents of the `.credentials` file:
 
     ```command
-    cat /etc/motd
+    cat /home/$USERNAME/.credentials
     ```
 
-1. Open your web browser and navigate to the Airflow URL provided in the last step. This should be the custom domain you entered during deployment or your Compute Instance's rDNS domain (such as `192-0-2-1.ip.linodeusercontent.com`). See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing the rDNS.
+This returns the admin password and other details that were automatically generated when the instance was deployed. Save them securely. After your credentials are saved, you can safely delete the file.
+
+## Getting Started After Deployment
+
+Once you have the credentials, you can access your Apache Airflow instance. Open a browser, and navigate to your Linode domain entered during deployment or the rDNS domain `https://203-0-113-0.ip.linodeusercontent.com`.
 
-1. Within the Airflow login prompt that appears, enter the credentials provided in a previous step and sign in.
+Within the Airflow login prompt that appears, enter the credentials provided in the `.credentials` file, and sign in.
 
-    ![Screenshot of the Airflow login prompt](airflow-login.png)
+![Screenshot of the Airflow login prompt](airflow-login.png)
 
-1. Once you are signed in, the Airflow dashboard appears. From here, you can view the DAGs (Directed Acyclic Graphs) and access all other areas of the dashboard.
+The Airflow dashboard appears once you're signed in. From here, you can view the DAGs (Directed Acyclic Graphs) and access all other areas of the dashboard.
 
-    ![Screenshot of Apache Airflow GUI](airflow-gui.png)
+![Screenshot of Apache Airflow GUI](airflow-gui.png)
 
-1. You can now start using Apache Airflow. If you are unfamiliar with it, consider reading through the official documentation or Linode's own guides:
+You can now start using Apache Airflow. If you are unfamiliar with it, consider reading through the official documentation or our provided guide:
 
-    - [Airflow > Tutorials](https://airflow.apache.org/docs/apache-airflow/stable/tutorial/index.html)
-    - [Airflow > How-to Guides](https://airflow.apache.org/docs/apache-airflow/stable/howto/index.html)
-    - [Create Connections and Variables in Apache Airflow](/docs/guides/apache-airflow-tutorial-creating-connections-and-variables/)
+- [Airflow > Tutorials](https://airflow.apache.org/docs/apache-airflow/stable/tutorial/index.html)
+- [Airflow > How-to Guides](https://airflow.apache.org/docs/apache-airflow/stable/howto/index.html)
+- [Create Connections and Variables in Apache Airflow](/docs/guides/apache-airflow-tutorial-creating-connections-and-variables/)
 
 {{< note type="warning">}}
-The Akamai Quick Deploy App app deploys Apache Airflow in standalone mode, suitable for development, testing, and initial configurations. Standalone mode is not recommended for [production deployments](https://airflow.apache.org/docs/apache-airflow/stable/production-deployment.html).
+This Akamai Quick Deploy App deploys Apache Airflow in standalone mode, suitable for development, testing, and initial configurations. Standalone mode is not recommended for [production deployments](https://airflow.apache.org/docs/apache-airflow/stable/production-deployment.html).
 {{< /note >}}
diff --git a/docs/marketplace-docs/guides/mastodon/index.md b/docs/marketplace-docs/guides/mastodon/index.md
@@ -2,7 +2,7 @@
 title: "Deploy Mastodon"
 description: "Learn how to deploy Mastodon, a decentralized social network and micro-blogging platform, on the Akamai Quick Deploy App."
 published: 2022-12-12
-modified: 2024-04-16
+modified: 2026-03-30
 keywords: ['social', 'messaging', 'mastodon']
 tags: ["linode platform","mastodon","quick deploy apps","cloud-manager",]
 external_resources:
@@ -24,11 +24,6 @@ Mastodon servers range in size from small private instances to massive public in
 
 {{% content "email-warning-shortguide" %}}
 
-{{< note >}}
-The Mastodon Quick Deploy App *requires* a custom domain. After deploying Mastodon, see the instructions within the [Configure Your Domain's Name Servers](#configure-your-domains-name-servers) section. Depending on a variety of factors, new and updated DNS records can take up to 48 hours to fully propagate, though it usually happens much sooner. The deployment fails if the DNS has still not been propagated.
-
-{{< /note >}}
-
 ## Deploying a Quick Deploy App
 
 {{% content "deploy-marketplace-apps-shortguide" %}}
@@ -41,68 +36,58 @@ The Mastodon Quick Deploy App *requires* a custom domain. After deploying Mastod
 
 ## Configuration Options
 
-- **Supported distributions:** Ubuntu 22.04 LTS
+- **Supported distributions:** Ubuntu 24.04 LTS
 - **Recommended minimum plan:** 2GB Shared CPU Compute Instance or higher
 
 ### Mastodon Options
 
 {{% content "marketplace-required-limited-user-fields-shortguide" %}}
 
-- **Domain** (*required*): The domain name you wish to use for the mastodon server, such as *example.com*.
-- **Linode API Token** (*required*): A personal access token for your account. The Linode API is used to create DNS records for your custom domain through the [DNS Manager](/docs/products/networking/dns-manager/). See [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/).
-- **Email for the Let's Encrypt certificate** (*required*): The email you wish to use when creating your TLS/SSL certificate through Let's Encrypt. This email address receives notifications when the certificate needs to be renewed.
-- **Username for the Mastodon Owner** (*required*): The username for the Owner user that will be created for the Mastodon server.
-- **Email Address for the Mastodon Owner** (*required*): The contact email for the Mastodon server's owner.
-- **Single-user mode** (*required*): Enabling Single User Mode prevents other users from joining the Mastodon Server.
+{{% content "marketplace-custom-domain-fields-shortguide" %}}
 
-## Getting Started after Deployment
-
-### Configure Your Domain's Name Servers
+{{% content "marketplace-special-character-limitations-shortguide" %}}
 
-To use Mastodon with the custom domain you specified during deployment, you must configure the domain to use Linode's name servers. This is typically accomplished directly through your registrar. See [Use Linode’s Name Servers with Your Domain](/docs/products/networking/dns-manager/guides/authoritative-name-servers/).
+#### App Options
 
-### View the Mastodon Site
+- **Email for the Let's Encrypt certificate** (*required*): The email you wish to use when creating your TLS/SSL certificate through Let's Encrypt. This email address receives notifications when the certificate needs to be renewed.
+- **Username for the Mastodon Owner** (*required*): The username for the owner user that will be created for the Mastodon server.
+- **Email Address for the Mastodon Owner** (*required*): The contact email for the Mastodon server's owner.
+- **Single-user mode** (*required*): Enabling Single User Mode prevents other users from joining the Mastodon Server.
 
-Open a web browser and navigate to the custom domain you entered when deploying Mastodon. This opens the Explore page in Mastodon, which displays public information about your site, public posts, and links to login or create an account.
+### Obtain the Credentials
 
-### Access Your Mastodon Account and Settings
+Once the app is deployed, you need to obtain the credentials from the server. To obtain the credentials:
 
-1. **Obtain and save passwords** that were generated on your behalf during deployment, including your Mastodon user's password.
+1. Log in to your new Compute Instance using one of the methods below:
 
-    1. Log in to your new Compute Instance through [Lish](/docs/products/compute/compute-instances/guides/lish/) or [SSH](/docs/guides/connect-to-server-over-ssh/) using the `root` user and the associated password you entered when creating the instance.
+    - **Lish Console**: Log in to Cloud Manager, click the **Linodes** link in the left menu, and select the Compute Instance you just deployed. Click **Launch LISH Console**. Log in as the `root` user. To learn more, see [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/).
+    - **SSH**: Log in to your Compute Instance over SSH using the `root` user. To learn how, see [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/).
 
-    1. The passwords have been saved in the /root/.deployment-secrets.txt file. You can view this file in your preferred text editor or through the `cat` command:
+2. Run the following command to access the contents of the `.credentials` file:
 
-        ```command
-        cat /root/.deployment-secrets.txt
-        ```
+    ```command
+    cat /home/$USERNAME/.credentials
+    ```
 
-        The file contains your PSQL password and user's (owner's) password.
+This returns the admin password and other details that were automatically generated when the instance was deployed. Save them securely. After your credentials are saved, you can safely delete the file.
 
-        ```file {title="/root/.deployment-secrets.txt"}
-        # BEGIN ANSIBLE MANAGED BLOCK
-        # PSQL password
-        password: WiLjKhJSZE01TW3AoqViN3Kglu2bidWt
-        # Owner password
-        password: 3c4a675311ee52c0c1d7173d5169a10d
-        # END ANSIBLE MANAGED BLOCK
-        ```
+## Getting Started after Deployment
 
-1. **Log in to Mastodon.** Within a web browser, navigate to `https://[domain.tld]/auth/sign_in`, replacing *[domain.tld]* with the custom domain you entered when deploying Mastodon. This opens the login page. Enter the owner's email address you created and the password that you obtained in the previous step. Once logged in, your user's home page is opened, which displays your own timeline, the post creation form, and links to navigate around.
+1. **Access Mastodon UI**. Open a web browser and navigate to `https://{{< placeholder "[domain.tld]" >}}/auth/sign_in`, replacing {{< placeholder "[domain.tld]" >}} with the domain you entered when deploying Mastodon or the rDNS domain `https://203-0-113-0.ip.linodeusercontent.com`. This opens the login page. Enter the owner's email address you created and the password that you obtained in the credentials file.
 
     ![Screenshot of the Mastodon user home page](mastodon-user-home.png)
 
-1. **Access admin settings**. Navigate to `https://[domain.tld]/admin/settings/` to view your site's administration settings. The administration page lets you alter the look, feel, and behavior of your site. Consider configuring each of these settings, including the site name, contact username, contact email, server description, and fields within other tabs.
+1. **Access admin settings**. Navigate to `https://{{< placeholder "[domain.tld]" >}}/admin/settings/` to view your site's administration settings. The administration page lets you alter the look, feel, and behavior of your site. Consider configuring each of these settings, including the site name, contact username, contact email, server description, and fields within other tabs.
 
     ![Screenshot of Mastodon admin page](mastodon-server-settings.png)
 
 1. The Mastodon instance also includes [Sidekiq](https://github.com/mperham/sidekiq) (background processing) and [PgHero](https://github.com/ankane/pghero) (a performance dashboard for Postgres). Both of these can be accessed through Mastodon Preferences page or by navigating to the following URLs:
 
-    - **Sidekiq:** `https://[domain.tld]/sidekiq`
-    - **PgHero:** `https://[domain.tld]/pghero`
+    - **Sidekiq:** `https://{{< placeholder "[domain.tld]" >}}/sidekiq`
+    - **PgHero:** `https://{{< placeholder "[domain.tld]" >}}/pghero`
 
 1. The Mastodon server is configured to send emails for actions such as new users signing up or resetting a password. The installation includes only minimal DNS records and there may be limited deliverability without further configuration. Review the guide to [Sending Email on Linode](/docs/products/platform/get-started/guides/send-email/) for more information on DNS configurations and email best practices.
 
-To learn more about Mastodon, check out the [official documentation](https://docs.joinmastodon.org/) and [Mastodon blog](https://blog.joinmastodon.org/) with news and articles related to Mastodon. You can engage with the Mastodon administrative community on [Mastodon’s discussion forum](https://discourse.joinmastodon.org/), where you can peruse conversations about technical issues and community governance. When you are ready to make your instance known to the world, you can add it to the list over at [Instances.social](https://instances.social/admin) by filling out the admin form.
+To learn more about Mastodon, check out the [official documentation](https://docs.joinmastodon.org/) and [Mastodon blog](https://blog.joinmastodon.org/) with news and articles related to Mastodon. Engage with the Mastodon administrative community on [Mastodon’s discussion forum](https://discourse.joinmastodon.org/), where you can peruse conversations about technical issues and community governance. When you are ready to make your instance known, you can add it to the list at [Instances.social](https://instances.social/admin) by filling out the admin form.
 
 {{% content "marketplace-update-note-shortguide" %}}