Cutover needs a redirect path for /packages/* and /bundles off mpak.dev
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cloud, github
- Domain
- infrastructure, web-dev
Research direction
Read issue #164's deploy-coupling section and the comment in apps/web/src/routes/bundles.tsx, then inspect the Pages and DNS cutover setup to identify where redirects can be handled. Name a mechanism that routes all 41 /packages/* URLs and /bundles from mpak.dev to their new home, add it to #164's deploy-coupling list, and confirm it before DNS moves.
Written by the indexing model from the issue text.
Description
Package pages are live on mpak.dev today:
$ curl -s -o /dev/null -w "%{http_code}\n" https://mpak.dev/packages/@nimblebraininc/echo
200
After the cutover in #164, mpak.dev is GitHub Pages and registry.mpak.dev serves the app. All 41 package URLs plus /bundles need to reach their new home, or they answer with the Pages 404.
Two things make this harder than the /sitemap.xml and /feed.xml items already listed in #164's deploy-coupling section:
- GitHub Pages cannot issue a 301. Serving a page at the old path or a meta-refresh shim passes far less link equity than a real redirect, so the mechanism likely has to sit in front of Pages (CloudFront) rather than in
mpak-web. /bundlesis linked from the marketing site, the docs, and CLI output, per the comment inapps/web/src/routes/bundles.tsx. The app redirects/bundlesto/on the new host, but nothing catches the old host's/bundles.
mpak-web PR #5 stands up the Pages deploy and touches no routing, so this is unowned right now.
Add /packages/* and /bundles to #164's deploy-coupling list with a named mechanism, and confirm it before DNS moves.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 13
- Avg merge
- 16m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NimbleBrainInc/mpak
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NimbleBrainInc/mpak#180 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NimbleBrainInc/mpak#175 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
NimbleBrainInc/mpak#159 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NimbleBrainInc/mpak#120 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
NimbleBrainInc/mpak#112 ·
All issues in NimbleBrainInc/mpak
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Comfy-Org/ComfyUI_frontend#23773 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34301 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/gh-aw-firewall#11797 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#7007 ·
Maintainers usually reply within 1 day