adam/ipfs-blog
1
0 Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-11-03 11:32:21 +01:00
Code Issues 17 Packages Projects Releases Wiki Activity

Launch cutover checklist #13

New Issue
Closed
opened 2026-10-05 05:09:19 +02:00 by adam · 11 comments
adam commented 2026-10-05 05:09:19 +02:00
Owner
Copy link
Copy source

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 https://github.com/ipfs/ipfs-blog/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 https://github.com/ipfs/ipfs-blog/issues/80
  • Make sure any Hugo redirects are migrated to Vuepress redirects (https://github.com/ipfs/ipfs-blog/pull/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 https://github.com/ipfs/website/pull/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

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)
Prior to launch, tentatively scheduled for 8 April 2021. ## For @jessicaschilling - [x] Update top-level README.md to reflect latest info: Vuepress specifics, deploy details, maintainership, etc - [x] Close or migrate any open issues from https://github.com/ipfs/blog/issues - [x] Make this repo public - [x] Add standard org-wide issue labels and issue templates - [ ] ~~Confirm RSS feed works as intended (close, but added additional https://github.com/ipfs/ipfs-blog/issues/119 for hotfix)~~ - [x] Protect `staging` branch so it can't be accidentally deleted upon merge? - [x] 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 https://github.com/ipfs/ipfs-blog/issues/80 - [x] Make sure any Hugo redirects are migrated to Vuepress redirects (https://github.com/ipfs/ipfs-blog/pull/93/ handles this) - [x] Ensure all content published to old blog since Feb 2021 has been migrated **(NOTE: new posts are scheduled for both 7 and 8 April)** - [x] Make sure Forestry UI link to image crop tool points to prod location - [x] Update repo description for go-live, not staging, links - [x] Countly: Duplicate test dashboard for prod (including 404 info) - [x] Countly: Set up dashboard/project view permissions and weekly email to relevant folks - [x] Update https://ipfs.io/media/ with press-kit info (@angiemaguire is reviewing https://github.com/ipfs/website/pull/421) - [x] Training: @jennwrites, @autonome, @angiemaguire, @emilymvaughan, @achingbrain - [x] Forestry permissioning: Investigate with @andyschwab whether this can be driven entirely from GitHub auth and groups; add users/roles as needed - [x] Sync staging and main one last time - [x] Send internal email and create meeting slide - [x] Write blog post ## For @jdiogopeixoto and/or @zebateira - [x] Confirm we won't accidentally spam Discourse when we cut over (or remediate) - [x] Remove ability to write directly to `main` from Forestry - [x] Change Fleek CANONICAL_BASE env variable (in both prod and staging) from https://ipfs-blog.on.fleek.co to to https://blog.ipfs.io - [x] Get Countly working in prod environment - [x] 404 page: [not working at the moment](https://ipfs-blog.on.fleek.co/asdf) – 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) - [x] add file `ipfs-404.html` to the root of the build folder - [x] add route `/404` instead of rendering it in the unknown route ## For others - [x] Confirm no URIs will break **(If everyone can lend a hand with this, would be ideal!)** - [x] DNS switching (@andyschwab): - [x] Stage a PR in infra repo for cutting over DNS - [x] Merge and confirm after approx 10min - [x] 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) <!-- github-sync-id:787084225 -->
adam closed this issue 2026-10-05 05:09:19 +02:00
adam commented 2026-10-05 05:09:20 +02:00
Author
Owner
Copy link
Copy source

@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 - 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. <!-- github-comment-id:800583266 -->
adam commented 2026-10-05 05:09:20 +02:00
Author
Owner
Copy link
Copy source

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.

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. <!-- github-comment-id:800644663 -->
adam commented 2026-10-05 05:09:21 +02:00
Author
Owner
Copy link
Copy source

One more to add to the list:

One more to add to the list: - [x] 404 page: [not working at the moment](https://ipfs-blog.on.fleek.co/asdf) – 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) - [x] add file `ipfs-404.html` to the root of the build folder - [x] add route `/404` instead of rendering it in the unknown route <!-- github-comment-id:807206781 -->
adam commented 2026-10-05 05:09:22 +02:00
Author
Owner
Copy link
Copy source

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).

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). <!-- github-comment-id:808154611 -->
adam commented 2026-10-05 05:09:22 +02:00
Author
Owner
Copy link
Copy source

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

@zebateira Correct on `https://ipfs-blog-staging.on.fleek.co`. There's no need to set up a staging sub-sub-domain. <!-- github-comment-id:808284153 -->
adam commented 2026-10-05 05:09:23 +02:00
Author
Owner
Copy link
Copy source

@jessicaschilling ok, then it's done:

image image
@jessicaschilling ok, then it's done: <img width="953" alt="image" src="https://user-images.githubusercontent.com/2353186/112654033-e671ba80-8e46-11eb-8a60-32157c2c16f5.png"> <img width="876" alt="image" src="https://user-images.githubusercontent.com/2353186/112654218-128d3b80-8e47-11eb-85d4-65b486f94e20.png"> <!-- github-comment-id:808303774 -->
adam commented 2026-10-05 05:09:24 +02:00
Author
Owner
Copy link
Copy source

@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 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. <!-- github-comment-id:808314689 -->
adam commented 2026-10-05 05:09:24 +02:00
Author
Owner
Copy link
Copy source

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

@jessicaschilling No, it's being used in our [vuepress config](https://github.com/ipfs/ipfs-blog/blob/main/src/.vuepress/config.js#L3) for the sitemap, robots and some other stuff. <!-- github-comment-id:808339792 -->
adam commented 2026-10-05 05:09:25 +02:00
Author
Owner
Copy link
Copy source

@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? 🙏

@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? 🙏 <!-- github-comment-id:808356959 -->
adam commented 2026-10-05 05:09:26 +02:00
Author
Owner
Copy link
Copy source

done 👍

done 👍 <!-- github-comment-id:808385209 -->
adam commented 2026-10-05 05:09:26 +02:00
Author
Owner
Copy link
Copy source

@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?

@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? <!-- github-comment-id:812020784 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/ipfs-blog#13