ports/security/acme.sh/files/acme-crontab.in
Dan Langille 678db807ed security/acme.sh: fix post-install script
The install script contained a syntax error which caused the log file
to not be created.

While here:

* rename script from pkg-install to pkg-post-install
* include another crontab example which provides additional contet to
  logging.

PR:		274348
2023-10-08 12:25:19 +00:00

30 lines
1.4 KiB
Text

#
# This file should be copied to %%PREFIX%%/etc/cron.d/acme
# use /bin/sh to run commands, overriding the default set by cron
#SHELL=/bin/sh
# mail any output to here, no matter whose crontab this is
#MAILTO=me@example.org
# uncomment, set mm and hh to the time (e.g. hh:mm) of day you want the
# cronjob to run - pick one of the following and enable it. Running more
# than one won't hurt, but you should avoid running them concurrently.
#
# the lockf ensures only one runs at a time if for some reason it never completes.
# I tend to do this for most cronjobs.
# This will send only errors to your email, everything else goes to /dev/null
# I find it lacks context.
mm hh * * * %%ACME_USER%% %%PREFIX%%/sbin/acme.sh --cron --home /var/db/acme/.acme.sh > /dev/null
#
# This dumps STDERR and STDOUT to a file and should never generate an email.
# The resulting log file shows any errors in context, which I found more useful for debugging.
# I set this file to rotate daily, since the cronjob also runs daily.
# I still get email if something goes wrong, via the SAVED_MAIL_FROM and
# SAVED_MAIL_TO options in account.conf - I also use NOTIFY_HOOK='pushover,mail'
# which requires setting SAVED_PUSHOVER_TOKEN and SAVED_PUSHOVER_USER.
#
mm hh * * * %%ACME_USER%% /usr/bin/lockf -t 0 /tmp/.acme.sh.cronjob %%PREFIX%%/sbin/acme.sh --cron --home /var/db/acme/.acme.sh > /var/log/acme.sh.cronjob.log 2>&1