nextcloud-cronjob/scripts/entrypoint.sh

#!/usr/bin/env bash
set -e

if [[ -z "$NEXTCLOUD_CONTAINER_NAME" ]]; then
    echo "NEXTCLOUD_CONTAINER_NAME is a required variable"
    exit 1
fi

echo "*/$NEXTCLOUD_CRON_MINUTE_INTERVAL * * * * /cron-tasks.sh" \
    > /var/spool/cron/crontabs/root

echo "Starting crond"
exec crond -f -l 0
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`#!/usr/bin/env bash`
Provide the ability to run user-defined cron tasks Mount individual shell scripts (with the `*.sh` extension) inside `/cron-scripts/` in the container. The cron daemon will automatically run these scripts inside the Nextcloud container for you. Write the scripts as if they will run in the Nextcloud container itself. 2018-12-07 00:30:27 +01:00			`set -e`
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00
			`if [[ -z "$NEXTCLOUD_CONTAINER_NAME" ]]; then`
			`echo "NEXTCLOUD_CONTAINER_NAME is a required variable"`
			`exit 1`
			`fi`

Cronjob works now between Nextcloud container recreation If the Nextcloud container is recreated while the cronjob container is still running, the ID of the container is obtained each time the cron tasks are executed. Previously it was cached on entrypoint, so if the ID changed this container would fail. 2019-06-21 02:15:55 +02:00			`echo "/$NEXTCLOUD_CRON_MINUTE_INTERVAL * * * /cron-tasks.sh" \`
Initial implementation of the nextcloud cronjob docker image 2018-12-02 02:08:31 +01:00			`> /var/spool/cron/crontabs/root`

Use tini as init for entrypoint script Signed-off-by: Robert Dailey <rcdailey@gmail.com> 2019-02-03 19:46:12 +01:00			`echo "Starting crond"`
			`exec crond -f -l 0`