Repository navigation
Conversation
Signed-off-by: henmohr <henriquemohr@redes.ufsm.br>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f13eaa4749
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| services: | ||
| postgres: | ||
| image: postgres:11-alpine | ||
| image: postgres:18-alpine |
There was a problem hiding this comment.
Migrate the volume before selecting PostgreSQL 18
When the repository-required bin/ncdd up path loads this file, every deployment still bind-mounts /var/lib/postgresql/data, but the PostgreSQL 18 image moved PGDATA to /var/lib/postgresql/18/docker and its declared volume to /var/lib/postgresql; its entrypoint treats the configured legacy mount as an unused/old database and exits. Consequently, both a fresh stack and an existing PostgreSQL 11 installation fail to start after pulling this change. Update the mount layout and provide an actual major-version data migration before selecting this tag, as required by the official image documentation.
AGENTS.md reference: AGENTS.md:L3-L3
Useful? React with 👍 / 👎.
| services: | ||
| postgres: | ||
| image: postgres:11-alpine | ||
| image: postgres:18-alpine |
There was a problem hiding this comment.
Update the deployment guides with the database upgrade
This tag change leaves both docs/deployment.md and docs/deployment_ptBR.md asserting that this Compose file currently uses postgres:11-alpine, while also warning users not to swap PostgreSQL majors against an existing data directory. Besides making the documented configuration inaccurate, omitting the required 11-to-18 migration procedure directs existing users into the startup failure introduced here; update both guides and include the supported migration steps with the image change.
Useful? React with 👍 / 👎.
No description provided.