Go-live checklist

Check your subscription plan

  • In the Control Panel, check the project’s Subscription, and that it includes the technical and support resources it will require once the site is live.

Dependencies

  • Consider pinning all dependencies. This will help ensure that future deployments do not introduce unexpected software updates.

DEBUG mode

  • Ensure that your Live server is configured to run with DEBUG = False (this is the default, but may have been changed during development).

Domains

Note

You may wish instead to follow these steps after conducting a live deployment. This will allow you to run performance and other checks on the live site while still using our private aldryn.io domain, so that your content is not exposed under your domain until you’re ready.

Environment variables

Serving configuration

  • Check the Aldryn Django addon configuration. We recommend the Has static filenames option, which lets you take advantage of caching.

Other settings

  • Check your project’s settings.py for any settings that may have been temporarily configured during development.

Deployment

  • Run a deployment of the Live server. If you have been using the Test server to build content prior to launch, us the Copy data from Test and deploy option.

After deployment

  • Run a crawler on the live site to check for broken links, such as the W3C Link Checker or the open-source LinkChecker application.
  • Check your site as a logged-in user, an anonymous user and in your browser’s private/incognito mode to verify expected behaviour.
  • Check response times with a tool such Pingdom.
  • If necessary, allocate more resources to the project via its Subscription and consult the How to fine-tune your server’s performance guide.