Skip to content

fix(docker): drop the standalone postgres and oracle compose files - #130

Merged
fjlopez merged 1 commit into
devfrom
fix/drop-standalone-compose
Oct 27, 2026
Merged

fjlopez merged 1 commit into
devfrom
fix/drop-standalone-compose

Conversation

@fjlopez

@fjlopez fjlopez commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Delete profiles/postgres/docker-compose.yml and profiles/oracle/docker-compose.yml. Their build context cannot see sitmun-shared. The profile directories stay, because the root Compose file mounts them through SITMUN_CONFIG_DIR.
  • The README and verify-compose-profiles.sh now start PostgreSQL and Oracle from the root Compose file.
  • check-compose-secrets.sh fails if either standalone file, the cd profiles/postgres instruction, or a verify-script target for those files comes back.

Test plan

  • The extended check failed while the two files, the README cd profiles/postgres step, and the verify-script targets were still present.
  • bash tools/scripts/check-compose-secrets.sh exits 0 after the deletion.
  • With the three secrets set, docker compose config for profiles/postgres.env and profiles/oracle.env resolves the backend to context ./back and backend/Dockerfile, and the proxy to proxy/Dockerfile.

Fixes #110

Those files built the backend and proxy from a context that cannot see
sitmun-shared. The root Compose file already runs the same services.

Fixes #110
@fjlopez
fjlopez merged commit 37ed7c9 into dev Oct 27, 2026
7 checks passed
@fjlopez
fjlopez deleted the fix/drop-standalone-compose branch November 1, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant