There's no Dockerfile, no docker-compose.yml, no Kubernetes manifests, and no documented deployment target beyond the implicit "this is a v0.app / Vercel-style Next.js app" per the README. Once real backend/database/cache dependencies exist (per the mock-db.ts and rates-cache issues above), deployment topology needs to be explicit.
Definition of done:
- Dockerfile producing a production build
- Documented (or codified via compose/manifests) topology showing this app's relationship to the real
backend service once integrated
Before opening a PR for this issue, read CONTRIBUTING.md.
This is not a starter-issue. The Definition of done above is the full
acceptance criteria, not a subset to sample from — a PR that addresses part
of it is an unfinished issue, not a smaller one. Your PR must include, in
the PR description itself:
PRs missing these will be sent back before review, not reviewed and rejected — please do this up front.
There's no Dockerfile, no docker-compose.yml, no Kubernetes manifests, and no documented deployment target beyond the implicit "this is a v0.app / Vercel-style Next.js app" per the README. Once real backend/database/cache dependencies exist (per the mock-db.ts and rates-cache issues above), deployment topology needs to be explicit.
Definition of done:
backendservice once integratedBefore opening a PR for this issue, read CONTRIBUTING.md.
This is not a starter-issue. The Definition of done above is the full
acceptance criteria, not a subset to sample from — a PR that addresses part
of it is an unfinished issue, not a smaller one. Your PR must include, in
the PR description itself:
PRs missing these will be sent back before review, not reviewed and rejected — please do this up front.