Staging Readiness
VPS smoke-test checklist for the demo build
Operational view for confirming the routed demo, health checks and dummy-data boundary before Steve and Craig receive staging access.
Recommended access
Tailscale-first private staging
Public HTTPS remains a later step after domain, DNS and Caddy setup are approved.
Smoke-Test Routes
Demo Access
/demo-accessWalkthrough entry point
Client Dashboard
/client-dashboardClient cohort view
Admin Dashboard
/admin-dashboardReviewer queue view
Candidate Detail
/candidates/amelia-hartExample candidate record
Report Preview
/reports/amelia-hartExample report preview
Staging Readiness
/staging-readinessDeployment smoke-test guide
Deployment Checks
Frontend route health
Confirm all shareable demo routes return HTTP 200 after deployment.
Backend health endpoint
Confirm the API responds at /health before sharing staging access.
Database privacy
Use the staging Compose file so PostgreSQL stays Docker-internal.
Dummy data boundary
Use only the seeded demo records and placeholder reviewer profiles.
Access method
Tailscale private access remains preferred until Ian approves public HTTPS.
Missing VPS details
Deployment still needs provider, IP, OS/version, SSH method and domain/Tailscale decision.
Local Ports
Required Inputs
VPS provider, public IP, OS/version, SSH username and access method.
Tailscale decision, domain/DNS decision and approval before package installation.
Next Operator Step
Deploy from the Git repository at D:\IntegrityScreen after replacing staging secrets and binding services to the approved private address.