Provision contact form: RATE_LIMIT KV, secrets, and reCAPTCHA keys - #15
Merged
Conversation
Wires up the last of the contact form's production dependencies: - Created and wired the RATE_LIMIT KV namespace into wrangler.toml (namespace IDs aren't secret, safe to commit). - Set the CONTACT_SENDER, CONTACT_RECIPIENT, and RECAPTCHA_SECRET Worker secrets in production. - Registered a reCAPTCHA v2 checkbox site and wired the public site key into local dev (.env, untracked) and CI preview builds (new PUBLIC_RECAPTCHA_SITE_KEY repo variable, consumed by preview-deploy.yml's build step). - Updated docs/SECURITY.md's "Open Items" note, now resolved. The contact form is fully functional in production for the first time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
🔍 Preview deployment: https://5aa3ce0b-blindtechmage-website.blindtechmage.workers.dev |
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
2 participants
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
RATE_LIMITKV namespace intowrangler.toml(namespace IDs aren't secret, safe to commit).CONTACT_SENDER,CONTACT_RECIPIENT, andRECAPTCHA_SECRETWorker secrets in production.blindtechmage.com,localhost) and wired the public site key into local dev (.env, untracked, plus a new.env.example) and CI preview builds (PUBLIC_RECAPTCHA_SITE_KEYrepo variable, consumed bypreview-deploy.yml's build step).docs/SECURITY.md's "Open Items" note — now resolved.The contact form is fully functional in production for the first time.
Test plan
npm run typechecknpm run lint(js + markdown)npm run build, confirmeddata-sitekeyin builtcontact/index.htmlmatches the real site keynpm run lint:htmlagainst built outputnpm run test:unit(26/26 passing)npx wrangler versions upload --dry-runagainst the built config, confirmed bothSESSIONandRATE_LIMITKV bindings resolve