Requirements
Prepare the host, storage, DNS, TLS, origins, ports, and secrets.
Prepare a build-capable host and the public routes required by the production Compose stack. Jetrepo does not publish minimum CPU, memory, disk, throughput, or build-duration figures; measure them for your workload.
Access
You need host, DNS, TLS, reverse-proxy, Google OAuth, and secret-storage administration.
Host and build context
- Install Docker Engine with the Compose plugin.
- Keep the full trusted release checkout available as the Docker build context.
- Allow image and package downloads during builds.
- Provide durable local storage for the three named volumes: Postgres, Redis AOF, and object storage.
- Provide a protected destination for operator-selected backups.
Check the host tooling before using project commands:
docker version
docker compose versionThese commands prove only that Docker is available; they do not validate Jetrepo or host capacity.
DNS, TLS, and routing
Provide distinct final HTTPS origins for:
| Public role | Container port |
|---|---|
| Admin app | 3000 |
| Core API | 3333 |
| Delivery API | 4000 |
| Image service | 8000 |
| Object S3 API | 9000 |
The optional object-storage console uses port 9001. Keep it private unless an explicit administration need and access control justify exposure. Never expose Postgres port 5432 or Redis port 6379.
Validate DNS, certificates, and proxy routing externally. Also prove that containers on the Compose network can resolve and reach the public object origin; Core API and Worker use that route even though object storage shares their host. Hairpin or split DNS may be required.
If preflight fails before data is created, remove the new proxy and DNS routes. Do not delete any existing volume.
Identity and secrets
Create a Google OAuth web client for the final Core API origin and choose one allowed Google Workspace domain. Store unique deployment secrets outside the checkout and shell history.
The production build pulls Node, distroless Node, Postgres, Redis, object-storage, and image-service images. Some third-party tags float, so record the resolved digests used by each deployment.
No proxy product, external storage replacement, multi-host cluster, Kubernetes layout, or capacity baseline is tested by this guide.