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.
. This will help ensure that future
deployments do not introduce unexpected software updates. pinning all dependencies
Ensure that your Live server is configured to run with
(this is the default,
but may have been changed during development).
DEBUG = False
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 (support article:
how to use
your own domain with Divio). 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
to SECURE_SSL_REDIRECT environment
Check the Aldryn Django addon configuration. We recommend the
option, which lets you take advantage of caching. Hash static filenames
Check your project’s
for any settings that may have been temporarily configured
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.
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
guide. How to fine-tune your server’s performance