summaryrefslogtreecommitdiff
path: root/doc/cronjob.markdown
diff options
context:
space:
mode:
authorFrederic Guillot <fred@kanboard.net>2016-01-27 21:45:37 -0500
committerFrederic Guillot <fred@kanboard.net>2016-01-28 08:40:27 -0500
commit32e4a932c801dfa6c52f6e8211a96bdb7849579d (patch)
tree895d519842c69369713eaf4d8e96b7a3a17c1f3d /doc/cronjob.markdown
parent320c7971f606a0c9caa4a20bcfcbc2fe2f6c9c00 (diff)
Added automatic actions based on a daily event
Diffstat (limited to 'doc/cronjob.markdown')
-rw-r--r--doc/cronjob.markdown32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/cronjob.markdown b/doc/cronjob.markdown
new file mode 100644
index 00000000..32f12888
--- /dev/null
+++ b/doc/cronjob.markdown
@@ -0,0 +1,32 @@
+Background Job Scheduling
+=========================
+
+To work properly, Kanboard requires that a background job run on a daily basis.
+Usually on Unix platforms, this process is done by `cron`.
+
+This background job is necessary for these features:
+
+- Reports and analytics (calculate daily stats of each projects)
+- Send overdue task notifications
+- Execute automatic actions connected to the event "Daily background job for tasks"
+
+Configuration on Unix and Linux platforms
+-----------------------------------------
+
+There are multiple ways to define a cronjob on Unix/Linux operating systems, this example is for Ubuntu 14.04.
+The procedure is similar to other systems.
+
+Edit the crontab of your web server user:
+
+```bash
+sudo crontab -u www-data -e
+```
+
+Example to execute the daily cronjob at 8am:
+
+```bash
+0 8 * * * cd /path/to/kanboard && ./kanboard cronjob >/dev/null 2>&1
+```
+
+Note: the cronjob process must have write access to the database in case you are using Sqlite.
+Usually, running the cronjob under the web server user is enough.