Agent/add notify push deployment#1
Conversation
…updates Bumps the composer group with 1 update in the /vendor-bin/psalm directory: [symfony/http-foundation](https://github.com/symfony/http-foundation). Bumps the composer group with 1 update in the /vendor-bin/phpunit directory: [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit). Updates `symfony/http-foundation` from 5.4.48 to 5.4.50 - [Release notes](https://github.com/symfony/http-foundation/releases) - [Changelog](https://github.com/symfony/http-foundation/blob/8.1/CHANGELOG.md) - [Commits](symfony/http-foundation@v5.4.48...v5.4.50) Updates `phpunit/phpunit` from 9.6.22 to 9.6.33 - [Release notes](https://github.com/sebastianbergmann/phpunit/releases) - [Changelog](https://github.com/sebastianbergmann/phpunit/blob/9.6.33/ChangeLog-9.6.md) - [Commits](sebastianbergmann/phpunit@9.6.22...9.6.33) --- updated-dependencies: - dependency-name: symfony/http-foundation dependency-version: 5.4.50 dependency-type: direct:development dependency-group: composer - dependency-name: phpunit/phpunit dependency-version: 9.6.33 dependency-type: direct:development dependency-group: composer ... Signed-off-by: dependabot[bot] <support@github.com>
…in/psalm/composer-c5767f55fa chore(deps-dev): bump the composer group across 2 directories with 2 updates
Signed-off-by: henmohr <henriquemohr@redes.ufsm.br>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 450c5dbcb4
ℹ️ 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".
| -e PORT=7867 \ | ||
| -v /path/to/nextcloud/config:/config:ro \ | ||
| notify_push:local \ | ||
| /config/config.php |
There was a problem hiding this comment.
Load fragmented Nextcloud configuration in the container
When a Nextcloud installation stores its database or Redis settings in sibling *.config.php fragments, this recommended command parses only the main file because loading fragments is opt-in via --glob-config (src/config.rs:101-103,233-239). The container then exits with missing configuration instead of reusing Nextcloud's settings; pass --glob-config before /config/config.php here and in the Compose command example.
Useful? React with 👍 / 👎.
| # um proxy web nas redes indicadas abaixo. | ||
| services: | ||
| notify_push: | ||
| image: "${NOTIFY_PUSH_IMAGE:-ghcr.io/librecodecoop/notify_push:edge}" |
There was a problem hiding this comment.
Pin the deployment image to the installed app version
For an installation using the supplied Watchtower label, this default automatically tracks edge, which the new workflow republishes on every push to main; once main advances to another app minor version, the daemon is upgraded independently of the installed Nextcloud app and notify_push:self-test reports a version mismatch (lib/SelfTest.php:213-220). Default the production overlay to a matching semver tag and make edge/automatic upgrades explicit opt-ins.
Useful? React with 👍 / 👎.
| cp docker-compose.example.yml docker-compose.yml | ||
| docker compose up -d --build |
There was a problem hiding this comment.
Connect the Compose example to database and Redis
Following the documented copy-and-up sequence unchanged starts only notify_push on Compose's isolated default network, while the service URLs name db and redis even though neither service nor an external network is defined. The daemon therefore fails its database/Redis connection and restarts indefinitely; either include those dependencies and networks or instruct users to merge the service into an existing stack and replace the addresses before running it.
Useful? React with 👍 / 👎.
No description provided.