You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
>**Tip**: You can use the default [values.yaml](values.yaml)
328
328
329
-
## Cronjob
329
+
## Cron jobs
330
330
331
-
This chart can utilize Kubernetes `CronJob` resource to execute [background tasks](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html).
331
+
To execute [background tasks](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html) by using system cron instead of default Ajax cron, set`cronjob.enabled` parameter to `true`. Background jobs are important for tasks that do not necessarily need user intervention, but still need to be executed frequently (cleaning up, sending some notifications, pulling RSS feeds, etc.).
332
332
333
-
To use this functionality, set`cronjob.enabled` parameter to `true` and switch background mode to Webcron in your nextcloud settings page.
334
-
See the [Configuration](#configuration) section for further configuration of the cronjob resource.
335
-
336
-
>**Note**: For the cronjobs to work correctly, ingress must be also enabled (set `ingress.enabled` to `true`) and `nextcloud.host` has to be publicly resolvable.
333
+
Enabling this option will create a sidecar container in the Nextcloud pod, which will start a [`crond` daemon](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#cron) responsible forrunning the Nextcloud cron.php script. At first launch, the background jobs modein your Nextcloud basic settings will automatically be set to ***Cron***.
0 commit comments