MLTSHP Launch Hitlist

Setup / Configuration

• Reconfigure for production site versus staging s/new\.//g
• Restore view stats from summary data
• Finish Stripe setup
  • identify any new subscription options
  • identify any custom payment options (donations, etc.)
  • Bank account
• Install letsencrypt SSL cert to NodeBalancer
• "new" instance of site for testing purposes
• Database export from MLKSHK
• Complete S3 copy of MLKSHK to MLTSHP
• Create and install new Twitter API keys using MLTSHPHQ Twitter account
• Determine license for Github project
• CDN service configured (Cloudflare + Varnish cache at Linode)
• Put something on our Tumblr blog

Development

• Refresh site graphics for Retina resolution and licensed character art.
• Update terms of service
• Fix view stats for members
• Update site design to be more mobile friendly (responsive design).
• New user onboard process - on logging in with a user that existed in MLKSHK, offer to restore their content.
• Lock down site so only authenticated users can view it. Perhaps allow limited access to (not sure if this is available to completely anonymous visitors or to people who create an account but haven't subscribed yet):
  • popular page
  • first page of each shake / user page (still need to allow this)
• Setup continuous integration tests with Travis CI
• Merge new browser plugin binaries pull request
• Decide on vocabulary for site ("shake" vs "shop") -- we're sticking with "shake"
• Configure app for newrelic
• Configure Docker Cloud for automated Docker image builds

Operations

• Point "mltshp.com" to Linode NodeBalancer (do this last!)
• Documentation for site operations - https://gitlab.com/mltshp/deployment/wikis/run-book
  • Database restore process (doc: use Linode's backup restore process from their automated daily backup)
  • Deployment process
  • Rollback process
• Make sure Linode availability alerts are going to the right people

Post Launch

• Review the list of featured shakes