Launch cutover checklist

[jessicaschilling]

Prior to launch, tentatively scheduled for 8 April 2021.

For @jessicaschilling

• Update top-level README.md to reflect latest info: Vuepress specifics, deploy details, maintainership, etc
• Close or migrate any open issues from https://github.com/ipfs/blog/issues
• Make this repo public
• Add standard org-wide issue labels and issue templates
• Confirm RSS feed works as intended (close, but added additional RSS Feed Issues #119 for hotfix)
• Protect staging branch so it can't be accidentally deleted upon merge?
• Confirm Discourse comments display as intended (this should cut over fine as we explicitly included the preview domains in Discourse prefs, but we'll want to remove that after launch). To confirm: blog.ipfs.io, both Fleek preview domains. NOTE that http://127.0.0.1:8080/ipns/blog.ipfs.io/ and http://blog.ipfs.io.ipns.localhost:8080 are being investigated in Enable comments when loaded via http://localhost:8080/ipns/blog.ipfs.io/ #80
• Make sure any Hugo redirects are migrated to Vuepress redirects (Update redirects #93 handles this)
• Ensure all content published to old blog since Feb 2021 has been migrated (NOTE: new posts are scheduled for both 7 and 8 April)
• Make sure Forestry UI link to image crop tool points to prod location
• Update repo description for go-live, not staging, links
• Countly: Duplicate test dashboard for prod (including 404 info)
• Countly: Set up dashboard/project view permissions and weekly email to relevant folks
• Update https://ipfs.io/media/ with press-kit info (@angiemaguire is reviewing Media page -> IPFS press kit ipfs-inactive/website#421)
• Training: @jennwrites, @autonome, @angiemaguire, @emilymvaughan, @achingbrain
• Forestry permissioning: Investigate with @andyschwab whether this can be driven entirely from GitHub auth and groups; add users/roles as needed
• Sync staging and main one last time
• Send internal email and create meeting slide
• Write blog post

For @jdiogopeixoto and/or @zebateira

• Confirm we won't accidentally spam Discourse when we cut over (or remediate)
• Remove ability to write directly to main from Forestry
• Change Fleek CANONICAL_BASE env variable (in both prod and staging) from https://ipfs-blog.on.fleek.co to to https://blog.ipfs.io
• Get Countly working in prod environment
• 404 page: not working at the moment – fleek uses ipfs under the hood, so the 404s only works if we setup it up ipfs-friendly (example: https://github.com/ProtoSchool/protoschool.github.io/pull/550/files)
  • add file ipfs-404.html to the root of the build folder
  • add route /404 instead of rendering it in the unknown route

For others

• Confirm no URIs will break (If everyone can lend a hand with this, would be ideal!)
• DNS switching (@andyschwab):
  • Stage a PR in infra repo for cutting over DNS
  • Merge and confirm after approx 10min
• Move https://github.com/ipfs/blog into ipfs-inactive org (@jessicaschilling will file a support ticket for this; it's not time-critical but let's at least get ticket in at launch time)

[andyschwab]

@jessicaschilling - Forestry permissions can use "Teams", which are very useful, but the Teams are internal to Forestry and not related to groups/teams in GitHub.

Of course, just because Forestry is configured doesn't mean GitHub users can't still make their own PRs directly using markdown like we always have. Forestry is more of a safety net for less technical users than a gatekeeper for the GitHub savvy.

[jessicaschilling]

Thanks @andyschwab - I feared that was the case re Forestry, but just wanted to confirm with someone who was likely to have dug in deeper. 😊 We've got Forestry's Teams set up and will just focus on keeping them well groomed!

Good reminder about just being able to bypass Forestry entirely and do things straight in the code.

[zebateira]

One more to add to the list:

• 404 page: not working at the moment – fleek uses ipfs under the hood, so the 404s only works if we setup it up ipfs-friendly (example: https://github.com/ProtoSchool/protoschool.github.io/pull/550/files)
  • add file ipfs-404.html to the root of the build folder
  • add route /404 instead of rendering it in the unknown route

[zebateira]

Question about "Change Fleek CANONICAL_BASE env variable (in both prod and staging) from https://ipfs-blog.on.fleek.co to to https://blog.ipfs.io"

Should the staging value be https://ipfs-blog-staging.on.fleek.co for staging? (or we could setup staging.blog.ipfs.io or similar).

[jessicaschilling]

@zebateira Correct on https://ipfs-blog-staging.on.fleek.co. There's no need to set up a staging sub-sub-domain.

[zebateira]

@jessicaschilling ok, then it's done:

[jessicaschilling]

@jdiogopeixoto Do you remember why we originally had this set up differently - was it to get the Discourse previews to work correctly? Just trying to figure out what will feel "broken" until we move the DNS.

[jdiogopeixoto]

@jessicaschilling No, it's being used in our vuepress config for the sitemap, robots and some other stuff.

[jessicaschilling]

@jdiogopeixoto @zebateira Given that this is feeding robots, we should refrain from making this change until right before cutover. @zebateira, can you please put it back? 🙏

[zebateira]

done 👍

[jessicaschilling]

@andyschwab Just a heads-up: We are targeting Wed 7 or Thur 8 April for the cutover (forgot about some national holidays due to Easter!) if that sounds OK by you?