Skip to content

Latest commit

 

History

History
44 lines (38 loc) · 2.98 KB

Launch.md

File metadata and controls

44 lines (38 loc) · 2.98 KB
Raw

Launch Process

SWS Developers: Please refer to internal Confluence documentation for more up to date step-by-step instructions for site launches.

A "Launch" is any change to a domain that can impact visitors.

Prerequisite: Set up blt/local.blt.yml to include the API key and secret so that you can connect to Acquia cloud API. Add the following snippet to local.blt.yml:

cloud:
  key: [your-api-key]
  secret: [your-api-secret

You can find your API key and secret from SWS credentials document or you can create your own API key/secret in your profile settings

Several days before

  1. Schedule the launch with the site owner including a content freeze the day of.
  2. Add the new domain to the production environment
  3. Schedule the release of the domain with the appropriate people.
    • Check who owns vhost and that it can be changed by SWS or AS Central Infrastructure Applications (CIA) (using one of the following methods):
      1. host foo.stanford.edu
      2. remctl tools proxy showdest foo.stanford.edu
      3. Use StanfordWhat
    • Search IT Services Virtual Hosting
    • If the vhost points to www-v6.stanford.edu or proxy-service.best.stanford.edu, then CIA can release it.
    • If it points to sites-lb-stanford.edu, then Shea or John can change the vhost. It does not require a SNOW request to CIA. See "Changing Vhosts on sites-lb", below.
    • Otherwise, we have to contact the owner of the record in NetDB (see StanfordWhat ) and have them release it. If the owner agrees to release the vhost, send an email to the owner and CC Malkiat Singh and let them sort it out.
  4. Add necessary redirects to the site.

Launch Day

  1. Wait for the Vhost release
  2. Add the new Vhost to the NetDB record
  3. Wait for the DNS Refresh. This occurs every half hour at :05 and :35 past the hour.
  4. Ensure the Vhost points to Acquia by pinging the url. ping newvhost.stanford.edu
  5. Execute the blt command blt humsci:launch-site [site_machine_name] and enter the new site domain. This command will configure necessary site configuration and clear caches.
  6. Submit the site to Google for indexing: steps to index
  • During the verification for Google indexing, choose the "HTML Tag" option. Set the value of the tag as a metatag:
    • drush @[sitename].prod cset metatag.metatag_defaults.global tags.google [tag_value]
    • Clear drupal and varnish caches for the site.
    • Add sitemap.xml as a path for Google indexing.

Here's a recording of a launch: https://stanford.zoom.us/recording/play/zHx3_5dHKH4r1MmnFYSa72SNOCCeJFviGK7-5AuHq9s9FMea_VWwmgBwzpUnMkGL