# Self-hosted mCaptcha (proof-of-work CAPTCHA) — node1 deployment. # # node1 runs services as plain docker-compose stacks behind host-level Caddy # (NOT Coolify, NOT Traefik) — same pattern as /opt/sentry. Caddy terminates # TLS and reverse-proxies captcha.saas-ctrl.com -> 127.0.0.1:7000. # # Deployed at /opt/mcaptcha on node1 (176.9.111.179). See README.md. # # IMPORTANT: # - The cache is `mcaptcha/cache` (Redis + mCaptcha's PoW module), NOT vanilla redis. # - mCaptcha terminates NO TLS (PROXY_HAS_TLS=true in .env; Caddy does TLS). # - Port is published on 127.0.0.1 only — Caddy reaches it locally, never public. # - Password inside DATABASE_URL (.env) MUST equal MCAPTCHA_PG_PASSWORD. name: mcaptcha networks: mcaptcha-net: name: mcaptcha-net volumes: mcaptcha-pg-data: name: mcaptcha-pg-data services: mcaptcha: image: mcaptcha/mcaptcha:latest@sha256:e94486fe8ae2549977d4245fd48c0cf53ea03092b8412bc283e8dd1c3ca27717 restart: unless-stopped networks: [mcaptcha-net] env_file: [.env] ports: - "127.0.0.1:7000:7000" depends_on: mcaptcha_postgres: condition: service_healthy mcaptcha_redis: condition: service_started mcaptcha_postgres: image: postgres:16-alpine@sha256:57c72fd2a128e416c7fcc499958864df5301e940bca0a56f58fddf30ffc07777 restart: unless-stopped networks: [mcaptcha-net] environment: POSTGRES_USER: postgres POSTGRES_DB: postgres POSTGRES_PASSWORD: ${MCAPTCHA_PG_PASSWORD} volumes: - mcaptcha-pg-data:/var/lib/postgresql/data healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres"] interval: 10s timeout: 5s retries: 10 mcaptcha_redis: image: mcaptcha/cache:latest@sha256:56cb11d8cffb04c00dc6008c08d795a61cdacaab388cababa3c52cfc2ec6cc7a restart: unless-stopped networks: [mcaptcha-net]