How to Set Up a Staging Environment on DigitalOcean App Platform

Download the doctl command-line tool from your DigitalOcean Control Panel under API > Tokens & Keys. Run the authentication command to connect your local environment to your DigitalOcean account:

doctl auth init

When prompted, enter your API token. This enables you to create projects and apps via terminal commands with full precision and automation capabilities.

Log in to the DigitalOcean Control Panel at cloud.digitalocean.com and navigate to the main Dashboard. Click the New Project button to open the project creation form. In the Environment dropdown, select Staging to tag this project for your staging environment. Enter a descriptive project name like myapp-staging-project and a purpose such as Staging environment for myapp. Click Create Project to finalize. The project now appears in your project list with the Staging environment tag.

For precision and automation, create your staging project using the doctl command:

doctl projects create --name "myapp-staging-project" --purpose "Staging environment for myapp" --environment "Staging"

The command returns a project ID (e.g., c4f2b0a8-6f17-4e6f-9b8f-1a2b3c4d5e6f) that you will need for subsequent app creation steps. Note this ID for later use in linking your staging app to this project.

Create a my-staging-app.yaml file in your repository root with your application configuration. This file defines services, environment variables, and deployment settings specific to staging:

name: myapp-staging services: - name: web source_dir: / github: repo: yourusername/yourrepo branch: staging envs: - key: DB_HOST value: staging-db.example.com - key: API_URL value: https://staging-api.example.com - key: APP_ENV value: staging

Connect the app to your staging Git branch (e.g., staging or develop) and set staging-specific environment variables for database hosts, API endpoints, and application environment flags. Sensitive variables can be encrypted via the UI after deployment.

Deploy your staging app using the specification file and link it to your staging project:

doctl apps create --spec /path/to/my-staging-app.yaml --project-id "c4f2b0a8-6f17-4e6f-9b8f-1a2b3c4d5e6f"

Replace the spec path with your actual file location and the project ID with the one from your staging project creation. The command returns an app ID (e.g., 01c03d96-43bb-4da9-ba54-0b215c44a498) confirming that your staging app is now organizationally linked to the Staging environment and ready for deployment.

In the DigitalOcean Control Panel, navigate to your staging project and click Create App. Select your GitHub repository and choose the staging or develop branch for auto-deployment. In the app creation wizard, update the app name to something like myapp-staging. Proceed through the configuration steps, ensuring your app is linked to the staging project. This UI-based approach provides visual confirmation at each step and is ideal for users less familiar with CLI tools.

In the App Platform dashboard, navigate to your staging app and open Settings > Environment Variables. Define staging-specific variables that differ from production, such as:

DB_HOST=staging-db.example.com API_URL=https://staging-api.example.com APP_ENV=staging NODE_ENV=staging

For sensitive values like database passwords or API keys, use the encrypted variable option in the UI. These variables ensure your staging app connects to staging databases and services rather than production systems, maintaining clean isolation between environments.

Create a separate managed database instance for staging or use a distinct database within an existing cluster. In the App Platform dashboard, navigate to your staging app's Resources tab and add a managed database connection. Configure the connection string to point to your staging database host. If you need production-like data for testing, carefully sync a recent dump from production to staging, but ensure you disable any automated email sending or external service triggers to prevent accidental notifications to real users.

In your staging app's Settings tab, enable Auto-deploy and configure it to trigger on pushes to your staging or develop branch. This automation ensures that every code change pushed to the staging branch automatically redeploys to your staging environment without manual intervention. Disable auto-deploy for your production app to maintain control over production deployments and prevent accidental pushes from automatically going live.

Access your staging app using its assigned domain (e.g., myapp-staging.ondigitalocean.app) and verify that all features work correctly with staging-specific configurations. Check that database connections point to staging databases, API calls use staging endpoints, and environment variables are correctly loaded. Monitor the app logs in the App Platform dashboard to identify any configuration errors or missing variables. Run your test suite against the staging environment to ensure feature parity with production before deploying to live users.