Commit Graph
4 Commits
Author SHA1 Message Date
zeekay 92369eb2ac fix: route _next assets to correct section origin via Referer header
Each federated docs section (IAM, KMS, Platform) builds unique layout
and page chunks that only exist on its CF Pages origin. The Worker was
routing all /_next/ requests to the main origin, causing 404s for
section-specific chunks (e.g. app/docs/layout-*.js), which crashed
client-side hydration and broke sidebar navigation.

Now the Worker checks the Referer header on /_next/ requests to
determine which section the browser is rendering, and routes to that
section's origin first, falling back to main if the asset is missing.
2026-03-11 08:12:57 -07:00
zeekay 85634290f6 fix: update platform-docs CF Pages origin to correct subdomain 2026-03-10 21:51:05 -07:00
zeekay a06f3bca39 feat: add platform federated docs + update IAM/KMS/Platform docs for upstream merges
- Add platform to CF Worker routing (platform-docs.pages.dev)
- Add platform section filter in source.config.ts
- Add platform asset prefix in next.config.ts
- Create deploy-platform-docs.yml workflow
- Update IAM docs: Kerberos/SPNEGO, LDAP attrs, wildcard scopes
- Update KMS docs: PAM discovery, ClickHouse, cert metadata, sub-orgs
- Update Platform docs: volume backups, rollback registry, AI assistant
2026-03-10 21:34:39 -07:00
zeekay 767548803d docs: update IAM documentation and service guides 2026-03-03 20:59:18 -08:00