Adds a dedicated nextcloud_cron service to the blueprint. This ensures background tasks run reliably every 5 minutes, resolving the "Ajax/webcron mode detected" warning and ensuring feeds/notifications stay up to date.
Greptile Summary
This PR adds a dedicated nextcloud_cron service to the nextcloud-aio blueprint, resolving the "Ajax/webcron mode detected" warning by running Nextcloud's background jobs via the official /cron.sh entrypoint on a 5-minute interval. The implementation correctly shares the nextcloud_data volume and MySQL credentials with the main service.
The new nextcloud_cron service uses the same nextcloud:stable image and shares the nextcloud_data volume, which is the standard pattern for cron in the official Nextcloud Docker documentation.
The service correctly uses entrypoint: /cron.sh, which is included in the official Nextcloud image and handles the scheduling loop internally.
Minor: the cron service does not declare a depends_on for the main nextcloud service, meaning it can start concurrently during first-run initialization; adding this dependency would improve startup ordering.
Confidence Score: 4/5
This PR is safe to merge; the change is a well-known pattern for Nextcloud cron and introduces no breaking changes.
The implementation follows the standard Nextcloud Docker cron pattern (shared volume + /cron.sh entrypoint). The only concern is the absence of depends_on: nextcloud, which is a soft startup-ordering issue rather than a correctness bug — cron.sh retries every 5 minutes, so transient failures during first-run init self-resolve.
No files require special attention beyond the single depends_on suggestion in blueprints/nextcloud-aio/docker-compose.yml.
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/766
**Author:** [@tobiasdalhof](https://github.com/tobiasdalhof)
**Created:** 4/2/2026
**Status:** ✅ Merged
**Merged:** 7/7/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `nextcloud-cron`
---
### 📝 Commits (1)
- [`26f52d2`](https://github.com/Dokploy/templates/commit/26f52d26657d6237aa5244bdfed5436254c9ae46) feat(nextcloud-aio): add nextcloud_cron service
### 📊 Changes
**1 file changed** (+16 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/nextcloud-aio/docker-compose.yml` (+16 -1)
</details>
### 📄 Description
Adds a dedicated `nextcloud_cron` service to the blueprint. This ensures background tasks run reliably every 5 minutes, resolving the "Ajax/webcron mode detected" warning and ensuring feeds/notifications stay up to date.
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a dedicated `nextcloud_cron` service to the `nextcloud-aio` blueprint, resolving the "Ajax/webcron mode detected" warning by running Nextcloud's background jobs via the official `/cron.sh` entrypoint on a 5-minute interval. The implementation correctly shares the `nextcloud_data` volume and MySQL credentials with the main service.
- The new `nextcloud_cron` service uses the same `nextcloud:stable` image and shares the `nextcloud_data` volume, which is the standard pattern for cron in the official Nextcloud Docker documentation.
- The service correctly uses `entrypoint: /cron.sh`, which is included in the official Nextcloud image and handles the scheduling loop internally.
- Minor: the cron service does not declare a `depends_on` for the main `nextcloud` service, meaning it can start concurrently during first-run initialization; adding this dependency would improve startup ordering.
<h3>Confidence Score: 4/5</h3>
This PR is safe to merge; the change is a well-known pattern for Nextcloud cron and introduces no breaking changes.
The implementation follows the standard Nextcloud Docker cron pattern (shared volume + /cron.sh entrypoint). The only concern is the absence of depends_on: nextcloud, which is a soft startup-ordering issue rather than a correctness bug — cron.sh retries every 5 minutes, so transient failures during first-run init self-resolve.
No files require special attention beyond the single depends_on suggestion in blueprints/nextcloud-aio/docker-compose.yml.
<sub>Reviews (1): Last reviewed commit: ["feat(nextcloud-aio): add nextcloud\_cron ..."](https://github.com/dokploy/templates/commit/26f52d26657d6237aa5244bdfed5436254c9ae46) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27159390)</sub>
> Greptile also left **1 inline comment** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/766
Author: @tobiasdalhof
Created: 4/2/2026
Status: ✅ Merged
Merged: 7/7/2026
Merged by: @Siumauricio
Base:
canary← Head:nextcloud-cron📝 Commits (1)
26f52d2feat(nextcloud-aio): add nextcloud_cron service📊 Changes
1 file changed (+16 additions, -1 deletions)
View changed files
📝
blueprints/nextcloud-aio/docker-compose.yml(+16 -1)📄 Description
Adds a dedicated
nextcloud_cronservice to the blueprint. This ensures background tasks run reliably every 5 minutes, resolving the "Ajax/webcron mode detected" warning and ensuring feeds/notifications stay up to date.Greptile Summary
This PR adds a dedicated
nextcloud_cronservice to thenextcloud-aioblueprint, resolving the "Ajax/webcron mode detected" warning by running Nextcloud's background jobs via the official/cron.shentrypoint on a 5-minute interval. The implementation correctly shares thenextcloud_datavolume and MySQL credentials with the main service.nextcloud_cronservice uses the samenextcloud:stableimage and shares thenextcloud_datavolume, which is the standard pattern for cron in the official Nextcloud Docker documentation.entrypoint: /cron.sh, which is included in the official Nextcloud image and handles the scheduling loop internally.depends_onfor the mainnextcloudservice, meaning it can start concurrently during first-run initialization; adding this dependency would improve startup ordering.Confidence Score: 4/5
This PR is safe to merge; the change is a well-known pattern for Nextcloud cron and introduces no breaking changes.
The implementation follows the standard Nextcloud Docker cron pattern (shared volume + /cron.sh entrypoint). The only concern is the absence of depends_on: nextcloud, which is a soft startup-ordering issue rather than a correctness bug — cron.sh retries every 5 minutes, so transient failures during first-run init self-resolve.
No files require special attention beyond the single depends_on suggestion in blueprints/nextcloud-aio/docker-compose.yml.
Reviews (1): Last reviewed commit: "feat(nextcloud-aio): add nextcloud_cron ..." | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.