Deployment Docs
This page documents the current production delivery path for the club site and docs.
Canonical Production URLs
https://hashpass.club- canonical club web app on GitHub Pageshttps://hashpass.club/documentation/- Docusaurus documentation on the same Pages artifacthttps://club.hashpass.tech- DNS alias that canonicalizes tohttps://hashpass.clubhttps://docs.hashpass.tech- DNS alias that canonicalizes tohttps://hashpass.club/documentation/
Deployment Model
The production site is published from a single GitHub Actions workflow:
apps/web-appbuilds the root site.apps/docsbuilds the documentation site under/documentation/.packages/infra/scripts/build-club-docs-site.shcombines both outputs into.site-artifacts/club-docs.actions/upload-pages-artifactandactions/deploy-pagespublish that artifact to GitHub Pages.
Route 53 handles the DNS layer:
hashpass.clubpoints at GitHub Pages using the GitHub Pages A and AAAA records.club.hashpass.techanddocs.hashpass.techare CNAME aliases to the canonical site.
The workflow lives in .github/workflows/deploy-club-docs.yml.
The docs build still uses HASHPASS_DOCS_URL=https://hashpass.club and HASHPASS_DOCS_BASE_URL=/documentation/ so all generated links are canonical on the production domain.
Current References
amplify/AMPLIFY-API-ROUTES.md- legacy Amplify API route reference../infra/env/ENVIRONMENT_VARIABLES.md- runtime variable matrix for mobile, club, and BSL releases
Notes
hashpass.clubis the canonical public URL.- DNS changes can take up to 24 hours to propagate.
- GitHub Pages custom domain settings must be configured in the repository settings before the DNS cutover is considered complete.
- Legacy SST club front door notes remain in
packages/infrafor historical reference. - Historical deployment notes and one-off incident writeups live in
archive/docs/.