Docs / Deployment and operations

Deployment and operations

Verify static assets, domains, logs, rollback procedures and mail integration.

Separate server code from browser assets

A Worker cannot use the browser DOM or persistent local disk. Ship browser JavaScript, CSS and images through the app’s static deployment path, and store runtime uploads in object storage. A command that deploys one Hono server bundle does not automatically upload every file in public.

Reuse the project’s existing frontend build and asset pipeline. Verify direct navigation and refresh behavior for every client-side route.

Deployment records and rollback

Terminal
joripspace deployments --project PROJECT --json
joripspace events --project PROJECT --event-type error
joripspace checkpoint list --project PROJECT
joripspace rollback --project PROJECT --deployment DEPLOYMENT_ID

Confirm the deployment ID before rolling back. A code rollback does not reverse database migrations, external payments or mail already sent. Check source, migration history and recovery procedures before deployment.

Connect a custom domain

Terminal
joripspace domains --project PROJECT
joripspace domain create --project PROJECT --hostname www.example.com
joripspace domain verify --project PROJECT --hostname www.example.com

Replace the hostname with a domain you control, add the returned CNAME target at your DNS provider and verify it. Wait for both DNS and HTTPS provisioning before treating the connection as complete.

Connect a mail provider

Terminal
joripspace mail connect --project PROJECT
joripspace mail status --project PROJECT
joripspace mail test --project PROJECT

Complete SMTP setup or Google consent on the returned JoripSpace page. Never paste mail passwords or keys into an agent conversation. Send a test to an address you control, and use an outbox with deduplication and retry handling for bulk mail.

Distinguish feature completion from production readiness

  • Run type checks, builds and functional tests, then check the live URL.
  • Test login, denied permissions, invalid input, concurrent updates and external API failures.
  • Inspect database query plans, pagination, file permissions and deletion flows.
  • Verify gateway test payments, duplicate confirmation, realtime recovery and actual cron execution.
  • Monitor usage and errors, and assign alerting, backup and recovery ownership.
  • Keep source, original configuration and lockfiles in Git while excluding Secrets and local credentials.

Record external integrations or load tests you could not run as unverified. A local example passing does not prove the whole customer application is production-ready.

View all docsOpen projects