1
0
mirror of https://github.com/zokradonh/kopano-docker.git synced 2026-08-23 14:22:54 +00:00

Misc changes (#268)

* fixes for setup-tools.sh

fixes https://github.com/zokradonh/kopano-docker/issues/266

* add startup tests for meet demo
* add architecture to contributing file
* define ical_listen for kopano-ical
* precreate database if it does not yet exist
* fix spelling
This commit is contained in:
Felix Bartels
2019-10-22 15:00:31 +02:00
committed by GitHub
parent 4dac253cf2
commit bcb0926c6d
33 changed files with 153 additions and 67 deletions
+2 -2
View File
@@ -6,7 +6,7 @@ Service to carry out repeating tasks within the Kopano environment. Takes care o
## Recurring tasks and maintenance tasks within Kopano
There are certain tasks within Kopano that either need to be executed once (like creating the public store when starting a new environment for the first time) or on a regular base (like syncing the internal user list with and external ldap tree). For convinience this project includes a "scheduler" container that will take care of this and that can be dynamically configured through env variables.
There are certain tasks within Kopano that either need to be executed once (like creating the public store when starting a new environment for the first time) or on a regular base (like syncing the internal user list with and external ldap tree). For convenience this project includes a "scheduler" container that will take care of this and that can be dynamically configured through env variables.
The container knows two kinds of cron jobs (the crontab syntax is used for actual jobs):
@@ -15,4 +15,4 @@ The container knows two kinds of cron jobs (the crontab syntax is used for actua
- `CRONDELAYED_KBACKUP=30 1 * * * docker run --rm -it zokradonh/kopano_utils kopano-backup -h`
- Jobs prefixed with `CRONDELAYED_` are only executed at the scheduled time.
Instead of using the internal scheduler one can also just use an existing scheduler (cron on the docker host for example) to execute these tasks.
Instead of using the internal scheduler one can also just use an existing scheduler (cron on the docker host for example) to execute these tasks.