# ============================================================================= # 개발 환경 — 이 repo의 compose 파일은 이것 하나다. # # docker compose up -d --wait app # 앱 컨테이너(기본 조립, local 런타임) # docker compose up -d --wait db # 뒷단 서비스 하나만(이름을 대면 그 profile이 켜진다) # docker compose --profile jpa --profile redis up -d --wait # 뒷단 서비스 묶음 # docker compose --profile '*' down # 내린다. 데이터까지 지우려면 down -v # # 내릴 때 --profile '*'를 붙인다. 붙이지 않으면 compose는 켜진 profile의 서비스만 내리므로, 이름으로 # 띄운 db 같은 profile 서비스가 남는다. # # 뒷단 서비스는 capability 이름의 profile로 고른다. profile을 대지 않으면 app만 뜬다. # # profile 서비스 쓰는 기능 # jpa db (PostgreSQL 16) JPA # redis redis (ACL 계정) Redis # kafka kafka Kafka 발행 # mongo mongo, mongo-rs-init MongoDB # objectstorage minio, minio-init 객체 저장소 # auth keycloak JWT 발급자 # mail mailpit (STARTTLS 필수) SMTP 발송 # # 이 파일이 마운트하는 보조 파일은 compose/ 아래에 있다. compose lane(테스트)은 이 파일을 바탕으로 # 쓰고, lane에만 필요한 overlay·smoke client·스키마 적용은 src/app-bootstrap/compose-lanes/에 있다. # 경로는 모두 이 파일이 있는 저장소 루트 기준이다. # # auth profile은 keycloak client secret 파일이 있어야 뜬다. lane은 실행마다 만들고 지운다. 손으로 띄울 # 때는 compose/keycloak/secrets/graphql-smoke-client-secret에 아무 값이나 한 줄 넣는다(그 폴더는 # Git이 무시한다). mail profile도 같다: compose/mailpit/tls/에 server.crt·server.key가 있어야 한다. # # Graceful-shutdown sync table (feature-container-runtime-contract D5): # App shutdown timeout : 30s (APP_SERVER_SHUTDOWN_TIMEOUT — SSOT: docs/registries/ # env-keys.yaml, owner feature-env-driven-runtime-configuration) # Async executor wait : 19s (AsyncExecutorConfig.AWAIT_TERMINATION_SECONDS) # Container preStop : 5s (handled by the orchestrator / stop_grace_period offset) # stop_grace_period : 60s (30s app drain + 19s async + 5s preStop + 6s safety margin) # # The drain and the async wait are consecutive, not concurrent: Spring finishes the lifecycle # phase (the web server's graceful drain) before it destroys the executor, which then waits for # its queue. A 40s grace let the container be killed 9s into that wait (07-07). # DeveloperExperienceContractTest fails when this value is below the sum. # # Memory limit (D4): # The container memory limit MUST be set for -XX:MaxRAMPercentage=75 to be meaningful. # Default 512m suits a small service; adjust per deployment. A compose lane that boots every # capability at once raises it for itself (compose-profile-contracts.json, appMemoryLimit). # ============================================================================= # The local MinIO runtime, used by the server below and by the lane's object storage smoke client. # # It is the image the MinIO qualification lanes measured, by the same digest: # src/adapter/outbound/objectstorage/src/test/resources/object-storage/minio-provider-evidence.json # records it with the conditional-write findings, and ComposeMinioImageMatchesEvidenceTest in that # leaf fails when this default (or the lane file's copy) and the evidence disagree. Change them # together. # # Source: pgsty/minio, a community fork on Docker Hub, after Docker Hub's minio/minio and quay.io # stopped serving MinIO images (review 05-09). cgr.dev/chainguard/minio measured the same but was # not chosen; the evidence file's rejectedCandidates says why. LOCAL_MINIO_IMAGE points this runtime # at a mirror; the lanes take OBJECT_STORAGE_MINIO_IMAGE, digest-checked. x-local-minio-image: &local-minio-image "${LOCAL_MINIO_IMAGE:-pgsty/minio@sha256:b6bfe7239bfc83fb90d31612d9704d86039dd714f7904b3f1ad68f211e602372}" services: app: build: context: src/ dockerfile: Dockerfile args: RELEASE_VERSION: "${RELEASE_VERSION:-0.0.1}" BUILD_VERSION: "${BUILD_VERSION:-0.0.1+0000000}" GIT_SHA: "${GIT_SHA:-0000000}" SOURCE_URL: "${SOURCE_URL:-https://example.invalid/ca-tmpl}" # default = the composition a service ships. scripts/run-compose-runtime-smoke.sh sets # qualification: every capability module present, each lane switching on what it tests. COMPOSITION: "${COMPOSITION:-default}" # The composition is in the tag, so a lane's qualification image is never reused as the # default one (Compose reuses a matching tag instead of building). image: caskeleton:${BUILD_VERSION:-0.0.1_local_0000000}-${COMPOSITION:-default} # Optional, because src/.env is operator input and a fresh clone does not have one. Before this # was marked optional, untracking that file made `docker compose config` fail outright on a # clone. The tracked contract is src/.env.example; copy it. A compose lane does not depend on it: # its values go into a generated `environment:` block, which outranks every env_file. env_file: - path: ./src/.env required: false ports: - "${APP_SERVER_PORT:-8080}:8080" # Management (health, info, prometheus — answered without authentication) on loopback only: # published on every interface it reaches the whole LAN (07-13). The smoke lanes read it from # inside the container, so they need no host port at all. - "127.0.0.1:9001:9001" environment: # Explicit, not inherited. A Compose profile selects services; it says nothing about which # environment the application believes it is in. The dev and prod-smoke lane overlays set # their own. SPRING_PROFILES_ACTIVE: "local" TZ: "UTC" LANG: "C.UTF-8" LC_ALL: "C.UTF-8" # Graceful shutdown — fallback matches the env-keys.yaml SSOT default (30s). # Override via .env or docker compose --env-file if you need a different value. APP_SERVER_SHUTDOWN_TIMEOUT: "${APP_SERVER_SHUTDOWN_TIMEOUT:-30s}" APP_SERVER_SHUTDOWN: "graceful" # The `db` service below, on the internal network. The default composition does not read # these; a service that selects the relational capability does. APP_DATASOURCE_URL: "jdbc:postgresql://db:5432/${POSTGRES_DB:-ca_skeleton}" APP_DATASOURCE_USERNAME: "${APP_DATASOURCE_USERNAME:-ca_skeleton}" APP_DATASOURCE_PASSWORD: "${APP_DATASOURCE_PASSWORD:-ca_skeleton}" # ---- Read-only root filesystem (D2) ------------------------------------- # The application must write only to the tmpfs mounts declared below. # /tmp — Tomcat basedir (see -Dserver.tomcat.basedir=/tmp in Dockerfile). # /var/tmp/heap — heap dump landing zone (see -XX:HeapDumpPath=/var/tmp/heap). read_only: true tmpfs: - /tmp:mode=1777,size=128m - /var/tmp/heap:mode=1777,size=512m # No volume: the shipped composition keeps nothing on disk. A capability that does brings its # mount in its own overlay, added with -f when the capability is selected, so this file never # names one (07-08). # ---- Memory limit (D4) -------------------------------------------------- # Must be set so -XX:MaxRAMPercentage=75 can compute a meaningful heap bound. mem_limit: 512m memswap_limit: 512m # ---- Graceful shutdown (D5) --------------------------------------------- # stop_grace_period = app drain (30s, env-keys SSOT) + async wait (19s) + preStop (5s) # + margin (6s) = 60s. stop_grace_period: 60s # ---- Health check ------------------------------------------------------- # The actuator readiness probe on the management port (9001). It answers under every runtime # (local, dev, prod), unlike the public health path, whose base path differs by runtime. healthcheck: test: - "CMD" - "wget" - "--no-verbose" - "--tries=1" - "--spider" - "http://localhost:9001/actuator/health/readiness" interval: 5s timeout: 3s start_period: 60s retries: 12 restart: unless-stopped networks: - caskeleton-infra # ---- PostgreSQL -------------------------------------------------------------- # Published on the loopback interface only, so a host-side run (`./gradlew :app-bootstrap:bootRun`, # IDE) reaches the same database the containerised app reaches over the internal network. The # port is the one src/.env.example's APP_DATASOURCE_URL names. db: profiles: - jpa image: postgres:16-alpine environment: POSTGRES_DB: "${POSTGRES_DB:-ca_skeleton}" POSTGRES_USER: "${APP_DATASOURCE_USERNAME:-ca_skeleton}" POSTGRES_PASSWORD: "${APP_DATASOURCE_PASSWORD:-ca_skeleton}" TZ: "UTC" volumes: - type: volume source: caskeleton-db-data target: /var/lib/postgresql/data ports: - "127.0.0.1:5433:5432" networks: - caskeleton-infra healthcheck: test: [ "CMD-SHELL", "pg_isready -U ${APP_DATASOURCE_USERNAME:-ca_skeleton} -d ${POSTGRES_DB:-ca_skeleton}", ] interval: 10s timeout: 5s retries: 5 start_period: 30s # ---- MongoDB ----------------------------------------------------------------- # A replica set of one. Single-node is still a replica set: transactions and change streams need # one, and a standalone mongod that "works for reads" is a deployment that discovers the # difference at the first transaction. mongo: profiles: - mongo image: mongo:8.0.16 command: ["mongod", "--replSet", "rs0", "--bind_ip_all"] volumes: - type: volume source: caskeleton-mongo-data target: /data/db networks: - caskeleton-infra healthcheck: test: ["CMD", "mongosh", "--quiet", "--eval", "db.adminCommand('ping').ok"] interval: 10s timeout: 5s retries: 10 start_period: 20s mongo-rs-init: profiles: - mongo image: mongo:8.0.16 depends_on: mongo: condition: service_healthy # Idempotent: rs.initiate() on an already-initiated set returns an error this swallows, so the # stack can be re-run against a surviving volume without a manual reset. command: - mongosh - --host - mongo - --quiet - --eval - >- try { rs.initiate({_id:'rs0',members:[{_id:0,host:'mongo:27017'}]}) } catch (e) { if (!/already initialized/i.test(e.message)) { throw e } } networks: - caskeleton-infra restart: "no" # ---- Kafka ------------------------------------------------------------------- kafka: profiles: - kafka image: apache/kafka:3.8.0 environment: KAFKA_NODE_ID: "1" KAFKA_PROCESS_ROLES: "broker,controller" KAFKA_LISTENERS: "PLAINTEXT://:9092,CONTROLLER://:9093" KAFKA_ADVERTISED_LISTENERS: "PLAINTEXT://kafka:9092" KAFKA_CONTROLLER_QUORUM_VOTERS: "1@kafka:9093" KAFKA_CONTROLLER_LISTENER_NAMES: "CONTROLLER" KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: "CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT" KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: "1" KAFKA_TRANSACTION_STATE_LOG_REPLICATION_FACTOR: "1" KAFKA_TRANSACTION_STATE_LOG_MIN_ISR: "1" networks: - caskeleton-infra healthcheck: test: ["CMD-SHELL", "/opt/kafka/bin/kafka-broker-api-versions.sh --bootstrap-server kafka:9092"] interval: 10s timeout: 10s retries: 12 start_period: 30s # ---- Redis ------------------------------------------------------------------- # Authenticated the way a deployment authenticates, with the lanes' test-fixture accounts: # compose/redis/acl/lane-fixture-accounts.acl, the same file the Redis topology lanes use, mounted # as it is rather than copied. It is not a deployment file — its passwords are public and it carries # a lane-only `+@all` account (compose/redis/acl/README.md). Its first line turns the passwordless # `default` user off, so the application connects as the named accounts the lane contract gives it # (compose-profile-contracts.json, $redisComment). # # This Redis was open and the lanes declared app.redis.authentication.anonymous-access-accepted. # The application then logged that trade, and the missing advanced account, as two startup # warnings — correctly, because in production both are risks — and every Redis lane failed its # "startup is silent" check. Quieting the warning would hide the same trade in production; the # lane now authenticates the way a deployment does instead. # # The passwords are the file's fixture values (compose/redis/acl/README.md); this container is # on the internal network only and publishes no port. redis: profiles: - redis image: redis:7.4 command: - redis-server - --appendonly - "no" - --save - "" - --aclfile - /etc/redis/acl/lane-fixture-accounts.acl volumes: - type: bind source: ./compose/redis/acl target: /etc/redis/acl read_only: true networks: - caskeleton-infra healthcheck: test: # As the application account: with `default` off, an unauthenticated PING answers NOAUTH. - "CMD-SHELL" - "[ \"$$(redis-cli --user ca-skeleton-application --pass fixture-application --no-auth-warning ping)\" = PONG ]" interval: 5s timeout: 3s retries: 12 start_period: 5s # ---- Mailpit — the reference SMTP relay ---------------------------------------- mailpit: profiles: - mail image: axllent/mailpit:v1.21 environment: MP_SMTP_AUTH_ACCEPT_ANY: "1" # MP_SMTP_AUTH_ALLOW_INSECURE is deliberately absent, and Mailpit refuses to start with both: # "TLS cannot be required with --smtp-auth-allow-insecure". It existed to permit credentials # over a plaintext connection, which is exactly what requiring STARTTLS removes the need for — # any AUTH now happens inside the TLS session. # STARTTLS, required. Not a hardening extra: SmtpProviderProperties.TlsMode has two members and # neither is plaintext, so the platform cannot describe an unencrypted relay at all. A stack # that wanted a plaintext Mailpit would be asking for a transport the type refuses to express, # and the honest way to satisfy it is to give the relay a certificate. MP_SMTP_TLS_CERT: /run/mailpit-tls/server.crt MP_SMTP_TLS_KEY: /run/mailpit-tls/server.key MP_SMTP_REQUIRE_STARTTLS: "true" volumes: # Generated per run by the qualification wrapper for the host name `mailpit`, and removed on # teardown, exactly like the PostgreSQL lane certificate. A committed test certificate is a # private key in Git. - type: bind source: ./compose/mailpit/tls target: /run/mailpit-tls read_only: true networks: - caskeleton-infra healthcheck: test: ["CMD", "/mailpit", "readyz"] interval: 5s timeout: 3s retries: 12 start_period: 5s # ---- MinIO ------------------------------------------------------------------- minio: profiles: - objectstorage image: *local-minio-image command: ["server", "/data"] environment: MINIO_ROOT_USER: "${MINIO_ROOT_USER:-caskeleton}" MINIO_ROOT_PASSWORD: "${MINIO_ROOT_PASSWORD:-caskeleton-local}" volumes: - type: volume source: caskeleton-minio-data target: /data networks: - caskeleton-infra healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 10s timeout: 5s retries: 10 start_period: 10s # Bucket and policy bootstrap. Not a substitute for the round trip: creating a bucket proves the # server accepts an admin command, not that an object survives being written and read back. minio-init: profiles: - objectstorage # The client from the same supplier as the server. cgr.dev/chainguard/minio-client was not used: # it has no shell, and the bootstrap below is a shell script. image: "${LOCAL_MINIO_MC_IMAGE:-pgsty/mc@sha256:ce62c9053c69ce12a527a322345b5ad9f44b5f8a7b8189f82e516f2e3f30f1d8}" depends_on: minio: condition: service_healthy entrypoint: ["/bin/sh", "/opt/minio/bucket-bootstrap.sh"] environment: MINIO_ENDPOINT: "http://minio:9000" MINIO_ROOT_USER: "${MINIO_ROOT_USER:-caskeleton}" MINIO_ROOT_PASSWORD: "${MINIO_ROOT_PASSWORD:-caskeleton-local}" MINIO_BUCKET: "${MINIO_BUCKET:-ca-skeleton-objects}" volumes: - type: bind source: ./compose/minio/init target: /opt/minio read_only: true networks: - caskeleton-infra restart: "no" # ---- Keycloak ---------------------------------------------------------------- keycloak: profiles: - auth image: quay.io/keycloak/keycloak:26.0 # The wrapper reads the client secret from a mounted file and execs kc.sh. The realm artifact # carries only a ${...} reference, so no secret value is in Git, in the rendered config, or on a # command line. entrypoint: ["/bin/bash", "/opt/keycloak-entrypoint/entrypoint.sh"] environment: KC_BOOTSTRAP_ADMIN_USERNAME: "${KEYCLOAK_ADMIN:-admin}" KC_BOOTSTRAP_ADMIN_PASSWORD: "${KEYCLOAK_ADMIN_PASSWORD:-admin}" KC_HEALTH_ENABLED: "true" volumes: - type: bind source: ./compose/keycloak/entrypoint.sh target: /opt/keycloak-entrypoint/entrypoint.sh read_only: true - type: bind source: ./compose/keycloak/realms target: /opt/keycloak/data/import read_only: true secrets: - keycloak-graphql-smoke-client-secret networks: - caskeleton-infra healthcheck: test: - "CMD-SHELL" - "exec 3<>/dev/tcp/127.0.0.1/9000 && echo -e 'GET /health/ready HTTP/1.1\\r\\nHost: localhost\\r\\nConnection: close\\r\\n\\r\\n' >&3 && cat <&3 | grep -q '\"status\": \"UP\"'" interval: 10s timeout: 5s retries: 20 start_period: 30s networks: caskeleton-infra: driver: bridge volumes: caskeleton-db-data: driver: local caskeleton-mongo-data: driver: local caskeleton-minio-data: driver: local secrets: keycloak-graphql-smoke-client-secret: file: ./compose/keycloak/secrets/graphql-smoke-client-secret