Staging Environments

Staging Environments

Test changes safely before pushing to production. BlitzPress creates a full clone of your site as a staging environment.

Creating a Staging Site

From your site’s detail page in the panel, click “Create Staging”. BlitzPress will:

1. Copy all WordPress files to /home/staging.{domain}/public_html/
2. Create a separate staging database with its own credentials
3. Clone your live database into the staging database
4. Update wp-config.php with staging database + separate Redis DB
5. Run search-replace to update all URLs (https://{domain} → https://staging.{domain})
6. Set blog_public = 0 so search engines don’t index staging
7. Create an OLS virtual host for the staging subdomain
8. Issue SSL certificate for staging.{domain}

Working with Staging

• The staging site is fully independent — install plugins, change themes, test updates
• Staging uses a separate Redis database (DB 15 by default) to avoid cache conflicts
• The staging URL follows the format: https://staging.{domain}

Push to Live

When you’re ready to deploy your staging changes to production:

1. Click “Push to Live” in the panel
2. BlitzPress automatically creates a backup of your live site first
3. Files and database are synced from staging to production
4. URLs are search-replaced back to the production domain
5. Caches are purged automatically

Deleting Staging

Click “Delete Staging” to remove the staging site completely — database, files, vhost, and SSL certificate are all cleaned up.