Files
tehran_tala/docker-compose.yml
T
s.esmaeiliandClaude Opus 5 2de90c6b35 docs(delivery): add a step-by-step quick start and a full pre-release section
1. "0. Quick start — run these in order" at the top of DELIVERY.md: five steps
   from an empty machine to a verified running stack, copy-pasteable, with no
   decisions to make. Covers which env vars must have a value (and how to
   generate the two JWT secrets), `pnpm build:release` BEFORE
   `docker compose build`, what the boot log should say, which banner is
   expected and which means a step was missed, and how to run the end-to-end
   check. Every command in it was executed verbatim to confirm it works.

2. "Before the real release" replaces the old three-item list:
   - A. blocking config: real JWT_SECRET and a SEPARATE JWT_CUSTOMER_SECRET,
     remove OTP_MASTER_CODE, configure the SMS credentials
   - B. credentials the reference leaked and that must be rotated (SEC-12,
     SEC-06) — same live accounts, never copied into this repo
   - C. parity work not finished: admin (financial documents, users and
     permissions incl. the still-open PERM-01, reports) and apps (MON-08 first,
     then STUB-05 SMS recipients, STUB-04, STUB-03, analytics), pointing at
     ISSUES.md for the rest

Also removed the obsolete `version:` key from docker-compose.yml, which printed
a deprecation warning on every compose command and made the checklist's output
noisy. Config re-validated.

Verified after these changes: container bundle is byte-identical to the local
release build (sha256 match), and that container was re-tested end to end:
compose e2e 32/32, complete-profile 38/38, report 40/40, expert login 36/36.
Locally: jest 54/54, build 5/5, typecheck clean on all four apps.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-23 02:38:00 +03:30

109 lines
3.7 KiB
YAML

# No `version:` key — it is obsolete in Compose v2 and only prints a warning on
# every command, which made the delivery checklist's output noisy.
services:
db:
image: docker.arvancloud.ir/postgres:15-alpine
container_name: goldbank_db
environment:
POSTGRES_USER: ${POSTGRES_USER:-postgres}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-postgres}
POSTGRES_DB: ${POSTGRES_DB:-goldbank}
ports:
- "${EXTERNAL_DB_PORT:-5432}:5432"
volumes:
- postgres_data:/var/lib/postgresql/data
restart: unless-stopped
healthcheck:
test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-postgres} -d ${POSTGRES_DB:-goldbank}"]
interval: 5s
timeout: 5s
retries: 12
api:
build:
context: ./apps/api
dockerfile: Dockerfile
container_name: goldbank_api
# Prisma connects on module init, so a not-yet-ready DB crash-loops the API.
depends_on:
db:
condition: service_healthy
environment:
- DATABASE_URL=${DATABASE_URL:-postgresql://postgres:postgres@db:5432/goldbank?schema=public}
- PORT=${PORT:-3000}
# Auth. Without these the API falls back to a well-known development
# secret, so set them in the deployment environment.
- JWT_SECRET=${JWT_SECRET:-}
- JWT_EXPIRES_IN=${JWT_EXPIRES_IN:-}
- JWT_CUSTOMER_SECRET=${JWT_CUSTOMER_SECRET:-}
- JWT_CUSTOMER_EXPIRES_IN=${JWT_CUSTOMER_EXPIRES_IN:-}
# ⚠ DELIVERY ONLY — a fixed OTP that signs in ANY active customer.
# Empty/unset disables it, which is the correct state for production.
# See ISSUES REL-01. Must be exactly 4 digits to be typable in the apps.
- OTP_MASTER_CODE=${OTP_MASTER_CODE:-}
# SMS. All blank = messages are logged, not sent; the API still boots (D20).
- SMS_PROVIDER=${SMS_PROVIDER:-}
- SMS_TREZ_URL=${SMS_TREZ_URL:-}
- SMS_TREZ_USERNAME=${SMS_TREZ_USERNAME:-}
- SMS_TREZ_PASSWORD=${SMS_TREZ_PASSWORD:-}
- SMS_TREZ_SENDER_LINE=${SMS_TREZ_SENDER_LINE:-}
# Admin mobiles told when a customer completes their profile (D22).
# Blank = nobody is notified; the upload still succeeds.
- PROFILE_ADMIN_MOBILES=${PROFILE_ADMIN_MOBILES:-}
# No host ports — Dokploy/Traefik routes by domain to container port 3000
expose:
- "3000"
# Uploaded files (product images, etc.) land in storage/uploads inside the
# container. Without a volume they vanish on every recreate/redeploy, and
# every UploadedFile/ProductImage row created before that would then point
# at a URL that 404s.
volumes:
- api_uploads:/app/storage/uploads
restart: unless-stopped
# The bare name "api" is ambiguous on Dokploy's shared network (other stacks
# register it too), which made nginx dial the wrong containers. Use a unique alias.
networks:
default:
aliases:
- goldbank-api
admin-panel:
build:
context: ./apps/admin-panel
dockerfile: Dockerfile
container_name: goldbank_admin_panel
# No host ports — Dokploy/Traefik routes by domain to container port 80
expose:
- "80"
restart: unless-stopped
depends_on:
- api
user-app:
build:
context: ./apps/user-app
dockerfile: Dockerfile
container_name: goldbank_user_app
# No host ports — Dokploy/Traefik routes by domain to container port 80
expose:
- "80"
restart: unless-stopped
depends_on:
- api
# Same copy-only nginx pattern as user-app; map a separate Dokploy domain to this service.
user-app-v2:
build:
context: ./apps/user-app-v2
dockerfile: Dockerfile
container_name: goldbank_user_app_v2
expose:
- "80"
restart: unless-stopped
depends_on:
- api
volumes:
postgres_data:
api_uploads: