TechTroop

TechTroop form Worker

This Worker receives the business-access and IT-professional application forms from the GitHub Pages site at techtroop.co.

Production architecture

TechTroop’s root-domain email remains on iCloud. Do not enable Cloudflare Email Routing for techtroop.co or replace its MX records. The Worker uses an existing Cloudflare-routed sender domain and cannot select a recipient from form data.

Data handling

All accepted form fields are sent in the notification email. R2 stores only idempotency records and professional résumé files. Résumé links are signed, private, and expire with the 30-day R2 lifecycle. Buckets must not have an r2.dev URL or public custom domain.

Both application types require three distinct follow-up date and time options within the next seven days. Dates are checked using the applicant’s selected continental U.S. time zone, and the options are included in the notification email for manual scheduling.

Professional applicants may optionally provide a public Credly profile URL. The Worker validates that it is an HTTPS credly.com/users/... URL and labels it as applicant-provided, unauthenticated evidence in the notification email. TechTroop does not scrape Credly or claim that the profile belongs to the application email.

Maintenance

The production wrangler.jsonc, local .dev.vars, Wrangler state, and dependencies are ignored. Copy wrangler.example.jsonc when configuring a new workspace. Use npm run check for a deployment dry run and npm run deploy to deploy after static review. Do not submit live forms as an automated test.

Rollback with npx wrangler versions list --config wrangler.jsonc, followed by npx wrangler rollback VERSION_ID --config wrangler.jsonc.