Folder: ops/compose/

What

ops/compose/ contains compose manifests and environment definitions for local/VPS runtime. This boundary currently has 7 direct file(s) and 0 direct subfolder(s).

Does

It packages operational runbooks, scripts, and deployment artifacts for runtime stewardship (dominant direct file kinds: .example:2, .env:2, .yml:2).

Why

Operational clarity is required for recoverability, incident response, and safe production changes.

Subfolders

• (no direct subfolders)

Files

• README.md — What: ops/compose/ contains compose manifests and environment definitions for local/VPS runtime. This boundary currently has 7 direct file(s) and 0 direct subfolder(s). Does: It packages operational runbooks, scripts, and deployment artifacts for runtime stewardship (dominant direct file kinds: .example:2, .env:2, .yml:2). Why: Operational clarity is required for recoverability, incident response, and safe production changes.
• dev.env.example — What: Source artifact for dev.env in ops/compose/dev.env.example. Does: Contributes implementation or support behavior for this runtime surface. Why: Maintains explicit ownership boundaries for faster agent orientation.
• dev.secrets.sops.env — What: Source artifact for dev.secrets.sops in ops/compose/dev.secrets.sops.env. Does: Contributes implementation or support behavior for this runtime surface. Why: Maintains explicit ownership boundaries for faster agent orientation.
• docker-compose.dev.yml — What: Configuration/data artifact for docker compose.dev in ops/compose/docker-compose.dev.yml. Does: Provides structured settings or metadata read by runtime and tooling. Why: Keeps behavior deterministic by centralizing non-code control values.
• docker-compose.prod.yml — What: Configuration/data artifact for docker compose.prod in ops/compose/docker-compose.prod.yml. Does: Provides structured settings or metadata read by runtime and tooling. Why: Keeps behavior deterministic by centralizing non-code control values.
• prod.env.example — What: Source artifact for prod.env in ops/compose/prod.env.example. Does: Contributes implementation or support behavior for this runtime surface. Why: Maintains explicit ownership boundaries for faster agent orientation.
• prod.secrets.sops.env — What: Source artifact for prod.secrets.sops in ops/compose/prod.secrets.sops.env. Does: Contributes implementation or support behavior for this runtime surface. Why: Maintains explicit ownership boundaries for faster agent orientation.