Docs / Deployment
DEPLOYMENT TEMPLATE — NOT A DEPLOYMENT CLAIM
⏱️ 2 min read · 346 words
Deployment
The repository is prepared for a conventional API + worker deployment.
Required infrastructure
- PostgreSQL with SSL;
- Redis;
- private encrypted object storage;
- Clerk;
- secrets manager;
- DNS/TLS;
- monitoring/alerting.
- runtime/app configuration;
DATABASE_URL,REDIS_URL;- Clerk;
- storage;
- malware scanning;
- OCR;
- LLM;
- email;
- billing;
- SMART JWKS public key metadata.
Optional/provider-dependent services include Google Document AI, Anthropic, SendGrid, and Paddle.
Production environment
The committed .env.example is a template only.
Key groups include:
Never put real secrets into the repository.
API/worker split
Use:
npm start
npm run worker
with START_EMBEDDED_WORKERS=false for the API service.
Deployment evidence
A production release should retain:
- build identifier;
- migration verification;
- API health;
- worker/queue health;
- backup and restore proof;
- rollback proof;
- monitoring alert test;
- production configuration preflight.