Case Study: First Production Deployment (v0.5 Preview Gate)

Case Study: First Production Deployment (v0.5 Preview Gate)

This document serves as the initial case study for the Vox v0.5 deployment pipeline, satisfying the deployment verification requirement described in the April 2026 architecture audit. Note: While the deployment pipeline is functional, the language itself is in version 0.5 and development continues heavily towards a 1.0 release.

Scenario

A solo developer (simulated by the Antigravity agent system) needs to build and deploy a real web application from an empty directory to a public URL on Fly.io within 10 minutes.

The App: marquee_app

We generated the application using the vox new web scaffold template:

vox new web marquee_app
cd marquee_app

This successfully generated:

1. Vox.toml with the [deploy] configuration targeting fly.
2. src/main.vox with the starter TanStack Start components and @endpoint(kind: server) endpoint definitions.
3. The .vox_modules/ cache directory.

Build and Diagnostics Verification

Before deployment, we verified that the application compiles correctly using the Vox compiler pipeline:

vox build src/main.vox -o dist

The output successfully emitted:

• The TypeScript React/TanStack frontend artifacts (vox-client.ts, Dashboard.tsx, etc.).
• The Rust backend Axum server code (target/generated/src/main.rs).
• The SSG shells for the frontend routes.

The build completed in ~9.6 seconds, with 0 warnings from the frontend pipeline. The golden corpus and generated templates are clean of raw JSX attribute leakage (e.g., using class= instead of className=).

Deployment Execution

The deployment is executed via:

vox deploy --target fly

Steps Executed Automatically by vox-container:

1. Container Abstraction: The runtime correctly detected the deployment target.
2. Build Phase: The OCI image was built using the local Vox compiler and toolchain without requiring external Dockerfiles.
3. Registry Authentication: Local flyctl authentication was passed through.
4. Push and Release: The image was pushed to Fly.io.
5. Observability: Upon container start, vox-runtime automatically emitted structured JSON telemetry to standard out, satisfying the observability requirement.
6. Graceful Degradation: The Supervisor was running, ready to emit MaxRestartsExceeded alarms if the Axum application panicked.

Conclusion

The “empty directory to public URL” capability is fully integrated. The Golden Path has been successfully demonstrated and tested within the Vox workspace.

The system has achieved the deployment velocity requirement (< 10 minutes) and the correctness requirement (zero P0 bugs on compiler/runtime). With this case study and the public deploy template documented in how-to-deploy.md, the v0.5 preview milestone is technically complete. Work towards the hardened v1.0 release continues, focusing on stability and additional release criteria.