Please follow the installation guide in the BlueSpice Helpdesk.
For an existing BlueSpice 4.5.x installation using an earlier stack of bluespice-deploy docker containers, an automated upgrade is possible.
In that case, ./bluespice-deploy up -d --profile=upgrade should be used.
Please check the upgrade guide for more information.
| Variable Name | Default Value | Description | Optional |
|---|---|---|---|
BLUESPICE_SERVICE_REPOSITORY |
bluespice |
pull Docker images from an alternative service repo | Yes |
BLUESPICE_WIKI_IMAGE |
edition-specific | use an alternative image for the wiki-containers | Yes |
COMPOSE_PROJECT_NAME |
bluespice |
use an alternate-docker-compose-name | Yes |
DATADIR |
./_volume |
Path to persitent Volumes | Yes |
ANTIVIRUS |
false |
enables ClamAV antivirus service | Yes |
LETSENCRYPT |
false |
enables LetsEcrpyt cert renew | Yes |
KERBEROS |
false |
enables Kerberos-Authentication | Yes |
TZ |
UTC |
Timezone for BlueSpice and container system time | Yes |
CHAT |
false |
enables Chat service connection | Yes |
AI |
false |
enables AI service connection | Yes |
For more variables to set in compose/.env, please also check documentation of the image behind the wiki-containers.
If the environment variable DEV_WIKI_DEBUG is set, one can set the debug-entrypoint GPC (=$_REQUEST) to a value matching the MW_ENTRY_POINT constant in context of the application to enable full debug log to stdout for any call to the specified entry point.
Please check the dev branch of this repo