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.
Consider pinning all dependencies. This will help ensure that future deployments do not introduce unexpected software updates.
Ensure that your Live server is configured to run with
DEBUG = False(this is the default, but may have been changed during development).
If you are using existing domains, prepare them for the switch. Ensure that they have low (less than 60 seconds) TTLs. High TTLs can cause problems when the domains are pointed at the new site, including delays in the automatic provisioning of SSL certificates.
Check that the live domain for the server is set up for the site in the Control Panel.
Check that any domains that should redirect to the primary domain are also set in the Domains setting in the Control Panel.
(For Aldryn projects) if required, enable redirects to HTTPS by setting the SECURE_SSL_REDIRECT environment variable to
Check that any other environment variables required on Live have been set (see: Environment variables).
Check the Aldryn Django addon configuration. We recommend the Hash static filenames option, which lets you take advantage of caching.
Check your project’s
settings.pyfor any settings that may have been temporarily configured during development.
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.
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.