URGENT: publish trust docs to correct repo (fix /docs/public/* + /.well-known/* 404)#63
Merged
Merged
Conversation
… /.well-known/*) PRs #3 and #4 on InstaNode-dev/web shipped these 7 files, but that repo has no GitHub Pages config. The publishing surface for instanode.dev is this repo (InstaNode-dev/instanode-web) — Pages source is main, path /, CNAME instanode.dev. Vite copies public/ verbatim into dist/ which Pages serves. Re-publishing the 7 files under public/docs/public/ + public/.well-known/ so the URLs Persona4 (InfoSec) and Persona2 (hobby dev) actually hit return 200. Files (all from the original landed-but-wrong-repo PRs, content unchanged except security.txt Expires bumped from 2027-05-13 → 2027-05-14): public/.well-known/pgp-key.txt (4096-bit RSA, fpr E950B348C79A...) public/.well-known/security.txt (RFC 9116) public/docs/public/dpa.md (controller-to-processor DPA + SCCs) public/docs/public/subprocessors.md (DigitalOcean, Razorpay, Brevo, etc.) public/docs/public/breach-notification.md (72h commitment + template) public/docs/public/security.md (bug-bounty intake + safe harbor) public/docs/public/trust-residency.md (NYC3 today, EU on roadmap) Verified locally: npm run build produces all 7 files under dist/ at the correct paths.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
InstaNode-dev/web, which has no GitHub Pages configuration. The publishing surface forinstanode.devis this repo (verified viagh api repos/InstaNode-dev/instanode-web/pages: sourcemain/, CNAMEinstanode.dev).public/verbatim intodist/, so dropping the 7 files underpublic/docs/public/andpublic/.well-known/makes them serve at the canonical URLs.security.txtExpires bumped from 2027-05-13 to 2027-05-14 to match the 12-month review window from today.Why this is urgent
Two customer journeys are currently rejected on this fix:
The 44349-byte response every URL returns right now is the GitHub Pages "Page not found" canary, confirming Pages is serving from the wrong (empty) source.
Files added (all under
public/so Pages serves them at root)/docs/public/dpa.mdpublic/docs/public/dpa.md/docs/public/subprocessors.mdpublic/docs/public/subprocessors.md/docs/public/breach-notification.mdpublic/docs/public/breach-notification.md/docs/public/trust-residency.mdpublic/docs/public/trust-residency.md/docs/public/security.mdpublic/docs/public/security.md/.well-known/security.txtpublic/.well-known/security.txt/.well-known/pgp-key.txtpublic/.well-known/pgp-key.txt(4096-bit RSA, fprE950B348C79A7E867867A76AEC2067042EA4BC23, expires 2028-05-14)Verification
npm run buildsucceeds locally; all 7 files land indist/at the expected paths.mainpush, thencurl -Iagainst each URL should return HTTP/2 200.Test plan
npm run buildproduces all 7 files underdist/.Deploy to GitHub Pagesworkflow onmain.curl -Iall 7 URLs returns 200.curl https://instanode.dev/.well-known/security.txtreturns the RFC 9116 contents.