Skip to main content

Pre-launch Configuration

Complete important configuration before launching your site.

This section provides information on how to enable backups, test your email plugin or module, review status reports, and test your cache.

Enable and Schedule Weekly Backups

  1. Click Backups on the Dev tab of your Site Dashboard then click Backup Schedule.

  2. Switch the toggle to Enable if needed, then pick the day on which you want to create weekly backups, and then click Update Weekly Backup Schedule.

  3. Repeat these steps for the Test and Live environments.

Refer to Backups Tool for more information on this feature.

Enable and Test Email Plugin/Module (Optional)

We strongly recommend using a third-party email service provider if your site will be sending outgoing email. Refer to Email on Pantheon for more information.


Some email solution providers (like Sendgrid) may implement a waiting period before upgrading to a paid plan, to fight malicious email. If you're switching email providers as part of your launch, make sure to research and plan for this if applicable.

Review Status Reports

Launch with confidence by taking advantage of Pantheon's static site analysis service for Drupal and WordPress.

  1. Access the Live environment in your Pantheon Site Dashboard.

  2. Navigate to the Status page.

The automated report will:

  • Check for exploited patterns in code

  • Show database stats

  • Reveal PHP errors

Refer to Drupal Launch Check and WordPress Launch Check for more information on what is included in these checks and how they work.

Maximize Performance by Configuring Cache (Optional)

Enable Object Cache

Pantheon's Object Cache) provides an alternative, drop-in caching backend for your website. This removes caching work from the database, which is vital for scaling to a larger number of logged-in users. It also provides a number of other features for developers, including managing queues and custom caching.

All paid plans except for a Basic plan can use Object Cache.

Configure Caching

Configure your performance settings to maximize performance.

Serving anonymous traffic from virtual memory allows a cached response to be returned to the browser without needing to access the application container, which in turns frees up resources to build more dynamic requests.

Test Cache

Follow the steps below to test Pantheon's Global CDN. This will show you whether or not a page is being served from Global CDN by examining the HTTP headers from a response using cURL.

  1. Examine the headers through the command line:

    curl --head
    HTTP/2 200
    content-type: text/html
    age: 2808
    cache-control: public, maxage=60
    expires: Thu, 21 Sep 2023 21:39:51 GMT
    last-modified: Thu, 21 Sep 2023 19:04:09 GMT
    via: 1.1 varnish, 1.1 varnish
    strict-transport-security: max-age=300
    date: Thu, 21 Sep 2023 21:26:39 GMT
    x-served-by: cache-bfi-krnt7300115-BFI, cache-bfi-krnt7300115-BFI
    x-cache: MISS, MISS
    x-cache-hits: 0, 0
    x-timer: S1695331600.573858,VS0,VE60

    Note the result for age or max-age.

  2. Navigate to the site's Dev environment and set the site to Maintenance Mode.

  3. Clear the cache from either the Advanced Page Cache module or from the Dashboard.

  4. cURL the site headers filtered for stale cache in a terminal:

    curl --head | grep PContext-Resp-Is-Stale

    If the response headers include PContext-Resp-Is-Stale, the page has been successfully served from stale cache.

More Resources