Skip to content

Launch Checklist Template (Drupal 7)

Gabe Carleton-Barnes edited this page Oct 17, 2017 · 1 revision

This is meant to be a complete list, and may not be relevant for all sites. Feel free to add items that come up.

Around a week before launch

  • Ensure all modules, libraries, and themes are pegged to a specific version or commit.
  • Confirm access to DNS control (CLIENT)
  • Lower TTL time in DNS settings to an hour or so, so that DNS updates will be quick. (CLIENT)
  • Pro Account on Pantheon (CLIENT)
  • Enable SSL on Pantheon or set up Cloudflare for free SSL.
  • Obtain SSL certificate (CLIENT w/ developer and/or Pantheon help) if not using Cloudflare.
  • Add performance and analytics modules (Google Analytics, Redis, entitycache, beancache, etc.)
  • Add image optimization module (tinypng_on_upload, kraken, etc.)
  • Enable and configure metatag modules (metatag, metatag_opengraph, metatag_twitter_cards, etc.)
  • Disable Dev modules
  • Turn off error reporting
  • Check/update admin user and default site email addresses
  • Remove test accounts or ensure passwords are secure (including admin account)
  • Set caching and and performance settings (see Pantheon status report for recommended settings)
  • Enable Redis Cache in Pantheon settings
  • Enable New Relic in Pantheon settings
  • Add redis settings to settings.php (Pantheon Redis Instructions) and revise hard coded paths in settings.php from "sites/all/modules" to "profiles/PROFILENAME/modules/contrib".
  • Schedule backups in Pantheon
  • Loadtest for clients that require it (requires many of the steps below to be complete)
  • Ensure client Typekit (or other hosted fonts) account has production domain in settings

Final launch items

  • Run final migration
  • Confirm payment processor is set to live mode
  • Google Analytics, Mailchimp, Mandrill, Mollom, Salesforce and other 3rd party integrations configured for live, in settings.php
  • Ensure SPF and DKIM authentication are configured for Mandrill email sending domain
  • Add domains to Pantheon
  • Ensure that SSL is enforced site-wide, or at least on all payment related pages
  • Test redirect code on live environment, by updating local hosts file
  • Add redirects from pages of old site in settings.php
  • Remove sitewide password protection
  • Update DNS to IP (if using SSL) or domain name listed in Pantheon control panel (CLIENT)

Domain related information to gather

Domain registration, DNS, Email, etc. is in the realm of the client or their sysamdin, not ThinkShout. This information is mainly so that we know where we fit in, and so the client is clear on what they need to do.

  • Domain registration: Where is it registered? Does it need to move to a different registrar?
  • Email: Where is email hosted? Will the site launch affect email routing and delivery?
  • DNS: Where is DNS handled? Do we update DNS at current DNS host, or use new DNS servers? Record anything special about current DNS entries.
  • Subdomains: Are there any subdomains used for separate things?
  • Additional domains: .net, .org, .info, etc.
  • SSL: Is SSL currently in use? Use existing cert? New cert needed?
  • Outside services: Do any outside services care about where the domain is hosted? e.g. signatures from server, or special key.

Client communication

  • Pantheon cost monthly: $100 for pro account + $30 for SSL ability.

Other examples, for reference

Clone this wiki locally