bluespice-deploy

Please read this guide carefully, before starting the update process.

DATADIR of bluespice/wiki container

There were some smaller changes in the directory layout. This sections describes the differences and explains required actions.

.
├── adminPassword
├── bluespice
│   ├── _sf_archive/
│   ├── _sf_instances/
│   ├── extensions
│   │   └── BlueSpiceFoundation
│   │       └── data/
│   ├── images/
│   ├── logs/
│   ├── post-init-settings.php
│   └── pre-init-settings.php
└── simplesamlphp
    ├── cache/
    ├── certs
    │   ├── saml.crt
    │   └── saml.pem
    ├── data/
    └── logs/

.
├── bluespice
│   ├── cache
│   ├── extensions
│   │   └── BlueSpiceFoundation
│   │       └── data/
│   ├── farm-archives/
│   ├── farm-instances/
│   ├── images/
│   ├── logs/
│   ├── oauth_private.key
│   ├── oauth_public.key
│   ├── post-init-settings.php
│   └── pre-init-settings.php
├── initialAdminPassword
└── simplesamlphp
    ├── cache/
    ├── certs/
    │   ├── saml.crt
    │   └── saml.pem
    ├── data/
    └── logs/

./adminPassword is now called ./initialAdminPassword
→ You can safely ignore this in the update case. The admin password is stored in the database and will not change during the update
./bluespice/_sf_archive/ and ./bluespice/_sf_instances/ are now called ./bluespice/farm-instances/ and ./bluespice/farm-archives/
→ You just need to rename the folders. No further changes within the folders are required.
There are no files ./bluespice/oauth_private.key and ./bluespice/oauth_public.key int the 4.5 directory.
→ They can be created, once the wiki-task container is running, using

bluespice-deploy exec wiki-task /app/bin/run-installation.d/040-create-oauth-keypair

PDF exclude - start

To submit feedback about this documentation, visit our community forum.

PDF exclude - end