Matchids Infrastructure

DevOps for Matchids: local development stack, deployment documentation, secrets management practices, monitoring/logging/backup/scaling notes. Phase 2 — built once the phase 1 product repos are solid, not before.

What's here

docker/
  docker-compose.dev.yml    Brings up Postgres + backend + web + admin locally
  Dockerfile.node-service     Reference Dockerfile for matchids-backend
  Dockerfile.next-app          Reference Dockerfile for matchids-web / matchids-admin
environments/
  README.md                  Development / staging / production overview
  .env.staging.example
  .env.production.example
scripts/
  check-env.sh                Verifies a repo's .env has every key its .env.example declares
docs/
  CI_CD.md
  SECRETS_MANAGEMENT.md
  MONITORING.md
  BACKUPS.md
  SCALING.md

Running everything locally

This assumes matchids-web, matchids-admin, matchids-backend, matchids-database, matchids-payments and matchids-celoht are cloned as sibling directories to this repo (see matchids-docs/development/GETTING_STARTED.md for the manual step-by-step version).

docker compose -f docker/docker-compose.dev.yml up

No secrets in this repo, or any Matchids repo

See docs/SECRETS_MANAGEMENT.md. Real credentials live in each developer's local .env, in CI's secret store, or in the hosting platform's secret manager — never here, never in any commit.

Independent deployability

Each application repo deploys on its own schedule (see docs/CI_CD.md) — this repo documents and scripts that process, it doesn't couple the services together at deploy time.