Update from 4.5 to 5.1

With version 4.5 of BlueSpice, there were two options for installation:

1. bluespice-deploy container stack
2. Classic tarball

Based on which of those you are starting from, the update to BlueSpice version 5.1 may require different steps.

Updating from bluespice-deploy 4.5

DATADIR of bluespice/wiki:4.5DATADIR of <code>bluespice/wiki:5.1Main differences

.
├── 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/

1. ./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
2. ./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.
3. 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