Docs / Deployment and operations

Deployment and operations

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

Separate server code from browser assets

An app has server code, browser assets and uploaded files. Deploy the Worker server code as a bundle, include JavaScript, CSS and images in the app’s static asset pipeline, and save uploads in project storage. Workers do not provide a browser DOM or persistent local disk. Prepare static asset delivery separately from the server bundle.

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.

Before you launch

  • 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.

Test the external services your app uses with real requests in their test environments. Load tests based on expected traffic and a recovery plan will help you respond to problems after launch.

View all docsOpen projects