fix(redirects): restore /installation as a redirect to the docs - #537
fix(redirects): restore /installation as a redirect to the docs#537fzipi wants to merge 1 commit into
Conversation
`/installation` was widely linked from blog posts before the documentation moved to the subsite, and has returned 404 ever since. The page now lives at /docs/1-getting-started/1-1-crs-installation/. A Hugo alias in the documentation repo cannot cover this: the docs are a separate build with baseURL /docs/, so an alias for /installation emits at /docs/installation/. Cloudflare Pages path redirects can, and static/_redirects is already used this way for the community call links. Both the slashed and unslashed forms are listed because Cloudflare matches the path literally, and 301 is explicit because the file's default is 302. Refs #64 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 51 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying website with
|
| Latest commit: |
ee56f2d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3fd0b5d0.website-1u6.pages.dev |
| Branch Preview URL: | https://fix-installation-alias-redir.website-1u6.pages.dev |
1 participant
what
Adds
/installation(and/installation/) tostatic/_redirects, pointing at/docs/1-getting-started/1-1-crs-installation/with a 301.why
/installationwas linked from a lot of blog posts before the documentation moved to the subsite,and has returned 404 ever since:
This is the third bullet of #64. A Hugo alias in the documentation repo cannot fix it: the docs are
a separate Hugo build with
baseURL .../docs/, so an alias for/installationis emitted at/docs/installation/, not at the site root. Cloudflare Pages path redirects can, andstatic/_redirectsis already used exactly this way for the community call links.details
docs treat
/trailingand/notrailing/as separate rules.301is explicit because the file's default status is 302 — worth knowing for the existing/register/*lines, which are currently temporary redirects./installationis included here. If other legacy top-level paths are worth preserving theycan go in the same block.
caveat
The destination embeds the docs' numbered path, so reorganising the documentation would leave this
pointing at a 404 without anything noticing —
_redirectsis a plain file, so the lychee linkchecker does not crawl it.