BlueSpice Helpdesk - User contributions [en]

Setup:Installation Guide/Docker

2024-12-10T08:04:34Z

Fspinar: fix pathes

{{Textbox
|boxtype=important
|header=Migration from 4.4
|text=With BlueSpice 4.5 there were some important changes to the container portfolio:
# There are no "all-in-one" containers anymore. Neither for FREE, nor for PRO and FARM editions
# The "distributed-services" setup for PRO and FARM edition has completely been reworked
If you are upgrading from one of the above-mentioned setups, please refer to the [[{{FULLPAGENAME}}/Migration_4.4 to 4.5|migration guide]]
|icon=yes
}}

__TOC__

===Overview===
Since version 4.5, BlueSpice MediaWiki can be easily installed using a stack of Docker container images. Everything is build in a modular way to allow different types of setups.

The most common cases are
# "All-in-one" (with and without Let's Encrypt)
# Custom database and search service
# Custom load balancer / proxy

=== Step 1: Get the stack ===
Get "docker-compose" files from https://bluespice.com/de/download/
wget <nowiki>https://bluespice.com/filebase/docker-deployment-script</nowiki> \
&& unzip docker-deployment-script \
&& cd docker-deployment-script/compose

The directory contains the following files:
{| class="wikitable"
|+
! style="width:350px;" |Filename
!Type
!Mandatory
!Comment
|-
| style="width:350px;" |<code>bluespice-deploy</code>
|bash-script
|false
|Wrapper for general start-up of needed containers
|-
| style="width:350px;" |<code>bluespice-prepare</code>
|bash-script
|false
|Prepare Folder and Permissions before first start also registers the service at the operating system
|-
| style="width:350px;" |<code>bluespice.service</code>
|service-script
|false
|Proper handling of the containers on reboot
|-
| style="width:350px;" |<code>docker-compose.main.yml</code>
|yml
|true
|Main application services/ run by <code>bluespice-deploy</code>
|-
| style="width:350px;" |<code>docker-compose.persistent-data-services.yml</code>
|yml
|false
|Database and search/ run by <code>bluespice-deploy</code>
|-
| style="width:350px;" |<code>docker-compose.stateless-services.yml</code>
|yml
|true
|PDF-Renderer/Cache/Formula/Diagram-Service
|-
| style="width:350px;" |<code>docker-compose.proxy.yml</code>
|yml
|false, but recommended
|Proxy Service
|-
| style="width:350px;" |<code>docker-compose.proxy-letsencrypt.yml</code>
|yml
|false
|Additional auto-renewal service for "Let's Encrypt" certificates
|-
| style="width:350px;" |<code>docker-compose.kerberos-proxy.yml</code>
|yml
|false
|Additional proxy for Kerberos based authenication
|}

For convenience, the <code>bluespice-deploy</code> script wraps the first four <code>yml</code> files by default. This includes the main wiki application and also required backend services, like a database, search and application cache.

Additional services can be loaded by adding <code>-f <filename> </code>.

Example:
bluespice-deploy \
-f docker-compose.proxy-letsencrypt.yml \
up -d

This will start the stack with "Let's Encrypt" certificates. For details, please refer to section [[#SSL certificates| SSL certificates]].

===Step 2: Set up environment variables===
Create <code>.env</code> file according to existing or state-to-be installation.

Example:
DATADIR=/data/bluespice
VERSION=4.5
EDITION=pro
BACKUP_HOUR=04

WIKI_NAME=BlueSpice
WIKI_LANG=en
WIKI_PASSWORDSENDER=no-reply@wiki.company.local
WIKI_EMERGENCYCONTACT=no-reply@wiki.company.local
WIKI_HOST=wiki.company.local
WIKI_PORT=443
WIKI_PROTOCOL=https

DB_USER=bluespice
DB_PASS=...
DB_HOST=database
DB_NAME=bluespice
DB_PREFIX=

SMTP_HOST=mail.company.local
SMTP_PORT=25
SMTP_USER=...
SMTP_PASS=...
SMTP_ID_HOST=...
{{Textbox|boxtype=note|header=Different editions|text=The example shows <code>EDITION=pro</code>. Be aware that for <code>pro</code> and <code>farm</code> you need to be logged into <code>docker.bluspice.com</code>.|icon=yes}}

=== Step 3: Prepare data directories===
Run <code>bluespice-prepare</code> script, helping you set up correct folder structure and permissions. Also installing a service for proper handling of the containers on reboots. Make sure to run this command with in a privileged user context (like <code>root</code>), as it will set permissions on the newly created directories.

=== Step 4: Start the stack ===
{{Textbox
|boxtype=important
|header=Initial installation
|text=When starting the stack the first time, the <code>wiki-task</code> container will automatically perform the installation. It may take a couple of minutes for the process to set up the database and complete. Once it is finished, the password for the default <code>Admin</code> user can be found in <code>$DATADIR/wiki/adminPasssword</code>.
|icon=yes
}}
Use <code>bluespice-deploy up -d</code> to start the stack, once the <code>.env</code> file and the "data directories" are ready. Once all containers are shown as "ready" you can navigate to <code>$WIKI_PROTOCOL://$WIKI_HOST:$WIKI_PORT</code> (e.g. <code><nowiki>https://wiki.company.local</nowiki></code>) in your favorite web browser and start using the application.

=== Additional options ===

==== SSL certificates ====
For using Let's Encrypt certificates just add <code>docker-compose.proxy-letsencrypt.yml</code> in your <code>bluespice-deploy</code> file.

{{Textbox
|boxtype=tip
|header=Self-signed certificates
|text=For using self-signend Certificates please put <code><bluespice-wiki.com>.crt</code> and <code><bluespice-wiki.com>.key</code> with the exact name of your Wikis URL in <code>${VOLUMES_DIR}/nginx/certs</code>
|icon=yes
}}

====Operating system level service====

{{Textbox
|boxtype=tip
|header=Adding additional services
|text=expand the <code>ExecStart</code> parameter in the <code>/etc/systemd/system/bluespice.service</code>
Example:
ExecStart=<WORKDIR>/bluespice-deploy -f docker-compose.proxy-letsencrypt.yml up -f -d --remove-orphans
|icon=yes
}}

==== Custom wiki application configuration ====
After the initial installation, the <code>${DATADIR}/wiki/bluespice/</code> contains two files that can be used to set custom application configuration as it may be found on [https://www.mediawiki.org mediawiki.org]:

* <code>pre-init-settings.php</code> - Can be used to set config that can be picked up by the init process
* <code>post-init-settings.php</code> - Can be used to manipulate configs that have been set by the init process

==== Custom database and search ====
If you have a MySQL/MariaDB and an OpenSearch server running in your local network, you can remove <code>docker-compose.persistent-data-services.yml</code> entirely from your <code>bluespice-deploy</code> file. Make sure to set the proper variables in the <code>.env</code> file.

====Kerberos proxy====
For implicit authenticationusing Kerberos, an additional proxy must be used: <code>bluespice/kerberos-proxy</code> . The file <code>docker-compose.kerberos-proxy.yml</code> contains a common configuration. It can be used '''instead of''' the regular <code>docker-compose.proxy.yml</code> file inside <code>bluespice-deploy</code> .

Make sure to have the files

* <code>${DATADIR}/kerberos/krb5.conf</code>
* <code>${DATADIR}/kerberos/kerberos.keytab</code>

set up properly.

The file <code>${DATADIR}/wiki/bluespice/pre-init-settings.php</code> can then be used to set up [[mediawikiwiki:LDAP_hub|"Extension:Auth_remoteuser" and the LDAP stack extensions]].

====SAML authentication====

During the initial installation a certificate for message signing will automatically be created. It can be found in <code>${DATADIR}/wiki/simplesamlphp/certs/</code>.

In order to configure a remote IdP, one must copy the IdP metadata XML to a file called <code>${DATADIR}/wiki/simplesamlphp/saml_idp_metadata.xml</code>. The SP metadata can then be obtained via <code><nowiki>https://{{$WIKI_HOST}}/_sp/module.php/saml/sp/metadata.php/default-sp</nowiki></code>. It must be configured in the remote IdP.

{{Textbox
|boxtype=tip
|header=Test authentication
|text= You can test authentication directly within the SimpleSAMLphp application. To do so, navigate to <code><nowiki>https://{{$WIKI_HOST}}/_sp/module.php/admin</nowiki></code> and log in with <code>admin</code> and the <code>INTERNAL_SIMPLESAMLPHP_ADMIN_PASS</code> found in <code>${DATADIR}/wiki/.wikienv</code>
|icon=yes
}}

Next, the extensions "PluggableAuth" and "SimpleSAMLphp" must be enabled on the wiki. To do so, add

<syntaxhighlight lang="php">
wfLoadExtensions( [
'PluggableAuth',
'SimpleSAMLphp'
] );
</syntaxhighlight>[[File:Setup:SAML ConfigManager EN 01.png|thumb|300x300px]]to the <code>${DATADIR}/wiki/bluespice/post-init-settings.php</code>. Run

./bluespice-deploy exec wiki-task /app/bluespice/w/maintenance/update.php --quick

to complete the installation.

After that, the authentication plugin configuration can be applied in [[Manual:Extension/BlueSpiceConfigManager|Special:BlueSpiceConfigManager]] under "Authentication".

==== OpenID Connect authentication ====

The extensions "PluggableAuth" and "OpenIDConnect" must be enabled on the wiki. To do so, add<syntaxhighlight lang="php">
wfLoadExtensions( [
'PluggableAuth',
'OpenIDConnect'
] );
</syntaxhighlight>to the <code>${DATADIR}/wiki/bluespice/post-init-settings.php</code>. Run

./bluespice-deploy exec wiki-task /app/bluespice/w/maintenance/update.php --quick

to complete the installation.

After that, the authentication plugin configuration can be applied in [[Manual:Extension/BlueSpiceConfigManager|Special:BlueSpiceConfigManager]] under "Authentication".

[[de:Setup:Installationsanleitung/Docker]]

Setup:Installation Guide/Docker

2024-09-13T12:51:01Z

Fspinar:

{{Textbox|boxtype=important|header=Migration from 4.4|text=With BlueSpice 4.5 there were important changes to the container portfolio:
# There are no "all-in-one" containers anymore. Neither for FREE, not for PRO and FARM editions
# The "distributed-services" setup for PRO and FARM edition has been reworked

If you are upgrading from one of the above-mentioned setups, please refer to the [[{{FULLPAGENAME}}/Migration_4.4 to 4.5|migration guide]]|icon=yes}}

== Overview ==
The BlueSpice application consists of a number of different services. To ease installations, they are available as a pre-configured stack at [https://github.com/hallowelt/bluespice-deploy github.com/hallowelt/bluespice-deploy], but they also allow more flexibility, e.g. by providing a simple way to run several services on different machines or to re-use existing services.
<drawio filename="Setup_Installation_Guide_Docker-01"></drawio>
{| class="wikitable"
|+
!Service name
!Description
!FREE
!PRO
!FARM
|-
| style="" class="col-turquoise-bg" |<code>wiki</code>
|The main application. It features two main modes: "web", for the connection to the client and "task" for any background processing and administrative purposes. It comes in different editions (FREE, PRO and FARM).
|YES
|YES
|YES
|-
| style="" class="col-turquoise-bg" |<code>pdf</code>
|Allows to create PDF filesfrom wikipages
|YES
|YES
|YES
|-
| style="" class="col-red-bg" |<code>search</code>
|Allows to perform a fulltext search on the wiki content
|YES
|YES
|YES
|-
| style="" class="col-turquoise-bg" |<code>formula</code>
|Allows to show mathematical and chemical formulas in the wiki content
|NO
|YES
|YES
|-
| style="" class="col-turquoise-bg" |<code>collabpads</code>
|Allows for simultaneous editing of wikipages
|NO
|YES
|YES
|-
| style="" class="col-red-bg" |<code>collabpads-database</code>
|Stores the data for simultaneous editing sessions.
|NO
|YES
|YES
|-
| style="" class="col-red-bg" |<code>diagram</code>
|Allows to create and edit diagram images in the wiki content
|NO
|YES
|YES
|-
| style="" class="col-turquoise-bg" |<code>pagepreview</code>
|Allows to show preview images of wikipages
|YES
|YES
|YES
|-
| style="" class="col-red-bg" |<code>cache</code>
|Supports application performance
|YES
|YES
|YES
|-
| style="" class="col-red-bg" |<code>database</code>
|Stores the application data
|YES
|YES
|YES
|-
| style="" class="col-turquoise-bg" |<code>proxy</code>
|Manages the clients's access to the different services. Provides SSL capabilities
|YES
|YES
|YES
|-
| style="" class="col-orange-bg" |<code>kerberos-proxy</code>
|Allows to set up a Kerberos-based authentication mechanism
|NO
|OPTIONAL
|OPTIONAL
|}
Generic services that can be substituted by already available ones are

* database →Can be replaced by any version compatible MariaDB / MySQL server
* collabpads-database →Can be replaced by any version compatible MongoDB server
* cache →Can be replaced by any version compatible MemcacheD server
* search →Can be replaced by any version compatible OpenSearch server
* proxy -> Can be replaced by any appropriately configured Proxy server / Loadbalancer

=== Installation ===
Get actual docker-compose-Files from https://bluespice.com/de/download/
wget <nowiki>https://bluespice.com/filebase/docker-deployment-script</nowiki> && unzip docker-deployment-script && cd docker-deployment-script/compose
{| class="wikitable"
|+
!Filename
!Type
!obligatory
!Comment
|-
|bluespice-deploy
|bash-script
|false
|Wrapper for general start-up of needed Containers
|-
|bluespice-prepare
|bash-script
|false
|Prepare Folder and Permissions before first start also creates service
|-
|bluespice.service
|service-script
|false
|Porper handling of the Containers on reboot
|-
|docker-compose.main.yml
|yml
|true
|Main Services/ run by bluespice-deploy
|-
|docker-compose.persistent-data-services.yml
|yml
|true
|Database and Search/ run by bluespice-deploy
|-
|docker-compose.stateless-services.yml
|yml
|false but strongly recommended for full functionality
|PDF-Renderer/Cache/Formula/Diagram-Service
|-
|docker-compose.proxy.yml
|yml
|false but recommended
|Proxy Service
|-
|docker-compose.proxy-letsencrypt.yml
|yml
|false
|Additional autorenewal service for LetsEncrypt-Certificates
|-
|docker-compose.kerberos-proxy.yml
|yml
|false
|Additional Proxy for Kerberos-Authenication
|}
The bluespice-deploy script starts the first 4 yml-Files by default.
% cat bluespice-deploy

docker compose \
-f docker-compose.main.yml \
-f docker-compose.persistent-data-services.yml \
-f docker-compose.stateless-services.yml \
-f docker-compose.proxy.yml \
$@
To add additional Services either change script or just add them by hand:
bluespice-deploy -f docker-compose.proxy-letsencrypt.yml up -d
for bluespice.service please do also either expand the line in the etc/systemd/system/bluespice.service:
[Unit]
Description=BlueSpice-Docker startup routinie
Requires=docker.service
After=docker.service

[Service]
WorkingDirectory=<WORKDIR>
ExecStart=<WORKDIR>/bluespice-deploy -f docker-compose.proxy-letsencrypt.yml up -f -d --remove-orphans
ExecStop=bluespice-deploy down
TimeoutStartSec=0
Restart=on-failure
StartLimitInterval=120
StartLimitBurst=2

[Install]
WantedBy=multi-user.target%
Create .env file according to existing or state-to-be Installation:
DATADIR=/data/bluespice
VERSION=4.5
EDITION=pro
BACKUP_HOUR=04

WIKI_NAME=BlueSpice
WIKI_LANG=en
WIKI_PASSWORDSENDER=wiki@localhost
WIKI_EMERGENCYCONTACT=wiki@localhost
WIKI_HOST=wiki.company.local
WIKI_PORT=443
WIKI_PROTOCOL=https

DB_USER=
DB_PASS=
DB_HOST=database
DB_NAME=bluespice
DB_PREFIX=

SMTP_HOST=
SMTP_PORT=
SMTP_USER=
SMTP_PASS=
SMTP_ID_HOST=
Run bluespice-prepare script, helping you set up correct Foder-Structure and Permissions. Also Installing a Service for proper handling of the containers on reboots.

=== Options: ===

===== SSL-Certificates =====
For using Let's Encrypt Certificates just adddocker-compose.proxy-letsencrypt.yml in your bluespice-deploy file

For using self-signend Certificates please put<code><bluespice-wiki.com>.crt</code> and <code><bluespice-wiki.com>.key</code> with the exact name of your Wikis URL in <code>${VOLUMES_DIR}/nginx/certs</code>

If Activating SSL after first creation of Wiki please change <code>$wgServer</code> in <code>${VOLUMES_DIR}/bluespice-data/LocalSettings.php</code>

to <code><nowiki>https://bluespice-wiki.com</nowiki></code>

also link your certificate to the bluespice-container in your docker-compose.yaml-File:

<code>- ${VOLUMES_DIR}/nginx/certs/<FQDNofyourWiki>.crt:/usr/local/share/ca-certificates/<FQDNofyourWiki>.crt:ro</code>

Please restart Containers after changing/adding SSL-Files

Setup:Installation Guide/Docker/Migration 4.4 to 4.5

2024-08-09T10:48:59Z

Fspinar:

== BlueSpice FREE "all-in-one" ==
===Data===
Data has been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/images/</code>
|<code>$DATADIR/bluespice/images/</code>
|
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|
|}

===Settings===
Data have been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
| Custom settings must be split up and added to those new files manually.
|}

==BlueSpice PRO "all-in-one"==
===Data===
Data has been stored in the directory referenced by <code>VOLUMES_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already. ATTENTION: needs migration
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/etc</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/mysql</code>
|<code>$DATADIR/database/data and</code> <code>$DATADIR/database/logs</code>
|No direct copy possible
|-
|<code>$VOLUMES_DIR/ssl</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:
wiki.example.com.crt/wiki.example.com.key
|-
|<code>$VOLUMES_DIR/postfix</code>
| -
|Obsolete. Fill in MailConfig in .env (SMTP*)
|-
|<code>$VOLUMES_DIR/startup</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|<code>Move $VOLUMES_DIR/etc/bluespice/bluespice.keytab here and rename it kerberos.keytab</code>
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env with relevant data. LocalSettings.php is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.d</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

Check your<code>$VOLUMES_DIR/bluespice/settings.d for custom changes like *.local.php files and or 070-LDAP.php, 09*-<some-name>.php</code>

==BlueSpice PRO "distributed-services"==
===Data===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.3 and 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
'''ATTENTION: might need migration'''
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/data</code>
|<code>$DATADIR/database/data</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/logs</code>
|<code>$DATADIR/database/logs</code>
|
|-
|<code>$DATADIR/proxy/certs</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:

* <code>wiki.example.com.crt</code>

* <code>wiki.example.com.key</code>
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env with relevant data. <code>LocalSettings.php</code> is not longer in use
Custom settings must be added to post-init-settings.php manually
|-
|<code>$VOLUMES_DIR/bluespice/settings.d</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be added to post-init-settings.php manually.
|}

[[de:Setup:Installationsanleitung/Docker/Migration_4.4_to_4.5]]

Setup:Installation Guide/Docker/Migration 4.4 to 4.5

2024-08-09T10:00:56Z

Fspinar: /* Settings */

== BlueSpice FREE "all-in-one" ==
===Data===
Data has been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/images/</code>
|<code>$DATADIR/bluespice/images/</code>
|
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|
|}

===Settings===
Data have been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
| Custom settings must be split up and added to those new files manually.
|}

==BlueSpice PRO "all-in-one"==
===Data===
Data has been stored in the directory referenced by <code>VOLUMES_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already. ATTENTION: needs migration
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/etc</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/mysql</code>
|<code>$DATADIR/database/data and</code> <code>$DATADIR/database/logs</code>
|No direct copy possible
|-
|<code>$VOLUMES_DIR/ssl</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:
wiki.example.com.crt/wiki.example.com.key
|-
|<code>$VOLUMES_DIR/postfix</code>
| -
|Obsolete. Fill in MailConfig in .env (SMTP*)
|-
|<code>$VOLUMES_DIR/startup</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|<code>Move $VOLUMES_DIR/etc/bluespice/bluespice.keytab here and rename it kerberos.keytab</code>
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env with relevant data. LocalSettings.php is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.d</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

Check your<code>$VOLUMES_DIR/bluespice/settings.d for local/custom changes. Special: *.local.php files and or 070-LDAP.php, 09*-<some-name>.php</code>

Nearly 99% of the persistant Files of

==BlueSpice PRO "distributed-services"==
===Data===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.3 and 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
'''ATTENTION: might need migration'''
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/data</code>
|<code>$DATADIR/database/data</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/logs</code>
|<code>$DATADIR/database/logs</code>
|
|-
|<code>$DATADIR/proxy/certs</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:

* <code>wiki.example.com.crt</code>

* <code>wiki.example.com.key</code>
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env with relevant data. <code>LocalSettings.php</code> is not longer in use
Custom settings must be added to post-init-settings.php manually
|-
|<code>$VOLUMES_DIR/bluespice/settings.d</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be added to post-init-settings.php manually.
|}

Setup:Installation Guide/Docker/Migration 4.4 to 4.5

2024-08-02T12:52:12Z

Fspinar: /* Data */

== BlueSpice FREE "all-in-one" ==
===Data===
Data has been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/images/</code>
|<code>$DATADIR/bluespice/images/</code>
|
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|
|}

===Settings===
Data have been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>.
{| class="cuscosky"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
| Custom settings must be split up and added to those new files manually.
|}

==BlueSpice PRO "all-in-one"==
===Data===
Data has been stored in the directory referenced by <code>VOLUMES_DIR</code>. Now <code>DATADIR</code> is used.
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already. ATTENTION: needs migration
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/etc</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/mysql</code>
|<code>$DATADIR/database/data and</code> <code>$DATADIR/database/logs</code>
|No direct copy possible
|-
|<code>$VOLUMES_DIR/ssl</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:
wiki.example.com.crt/wiki.example.com.key
|-
|<code>$VOLUMES_DIR/postfix</code>
| -
|Obsolete. Fill in MailConfig in .env (SMTP*)
|-
|<code>$VOLUMES_DIR/startup</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|<code>Move $VOLUMES_DIR/etc/bluespice/bluespice.keytab here and rename it kerberos.keytab</code>
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env wiht relevant data. LocalSettings.php is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.d</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

Check your <code>$VOLUMES_DIR/bluespice/settings.d for local/custom changes. Special: *.local.php files and or 070-LDAP.php, 09*-<some-name>.php</code>

Nearly 99% of the persistant Files of

==BlueSpice PRO "distributed-services"==
===Data===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.3 and 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. Cache folder has no persistent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
'''ATTENTION: might migration'''
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/data</code>
|<code>$DATADIR/database/data</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/logs</code>
|<code>$DATADIR/database/logs</code>
|
|-
|<code>$DATADIR/proxy/certs</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:

* <code>wiki.example.com.crt</code>

* <code>wiki.example.com.key</code>
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|
|}

Additional for Farm:

{| class="cuscosky"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$DATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="cuscosky"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env wiht relevant data. <code>LocalSettings.php</code> is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

Setup:Installation Guide/Docker/Migration 4.4 to 4.5

2024-07-23T07:59:19Z

Fspinar: /* BlueSpice PRO "all-in-one" */

== BlueSpice FREE "all-in-one" ==
===Data===
Data has been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>. Now <code>DATADIR</code> is used.
{| class="wikitable"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/images/</code>
|<code>$DATADIR/bluespice/images/</code>
|
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/cache/</code>
|
|Obsolete. CacheFolder has no persitent data
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already.
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|
|}

===Settings===
Data have been stored in the directory referenced by <code>WIKI_INSTALL_DIR</code>.
{| class="wikitable"
|+
!OLD (<code>bluespice/bluespice-free</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$WIKI_INSTALL_DIR/www/bluespice/w/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
| Custom settings must be split up and added to those new files manually.
|}

==BlueSpice PRO "all-in-one"==
===Data===
Data has been stored in the directory referenced by <code>VOLUMES_DIR</code>. Now <code>DATADIR</code> is used.
{| class="wikitable"
!OLD (<code>bluespice/bluespice-pro</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. CacheFolder has no persitent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already. ATTENTION: needs migration
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/etc</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/mysql</code>
|<code>$DATADIR/database/data and</code> <code>$DATADIR/database/logs</code>
|No direct copy possible
|-
|<code>$VOLUMES_DIR/ssl</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:
wiki.example.com.crt/wiki.example.com.key
|-
|<code>$VOLUMES_DIR/postfix</code>
| -
|Obsolete. Fill in MailConfig in .env (SMTP*)
|-
|<code>$VOLUMES_DIR/startup</code>
| -
|Obsolete
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|<code>Move $VOLUMES_DIR/etc/bluespice/bluespice.keytab here and rename it kerberos.keytab</code>
|}

Additional for Farm:

{| class="wikitable"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$VDATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="wikitable"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env wiht relevant data. LocalSettings.php is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

==BlueSpice PRO "distributed-services"==
===Data===
{| class="wikitable"
!OLD (<code>bluespice/bluespice-pro</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/logs/</code>
| -
|Obsolete. New containers log everything to <code>stderr</code> / <code>stdout</code>
|-
|<code>$VOLUMES_DIR/bluespice/images/</code>
|<code>$DATADIR/wiki/bluespice/images/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/cache/</code>
|
|Obsolete. CacheFolder has no persitent data
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/config/</code>
| -
|Obsolete. All contents of this directory have been migrated to the database in <code>4.4</code> already. ATTENTION: might migration
|-
|<code>$VOLUMES_DIR/bluespice/extensions/BlueSpiceFoundation/data/</code>
|<code>$DATADIR/wiki/bluespice/extensions</code><code>/BlueSpiceFoundation/data/</code>
|
|-
|<code>$VOLUMES_DIR/backup</code>
|<code>$DATADIR/wiki/backup</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/data</code>
|<code>$DATADIR/database/data</code>
|
|-
|<code>$VOLUMES_DIR/mariadb/logs</code>
|<code>$DATADIR/database/logs</code>
|
|-
|<code>$DATADIR/proxy/certs</code>
|<code>$DATADIR/proxy/certs</code>
|Name CRT and Key file after URL:
wiki.example.com.crt/wiki.example.com.key
|-
|<code>$VOLUMES_DIR/kerberos</code>
|<code>$DATADIR/kerberos</code>
|
|}

Additional for Farm:

{| class="wikitable"
!OLD (<code>bluespice/bluespice-farm</code> 4.2 and 4.3)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/_sf_instances/</code>
| <code>$VDATADIR/wiki/bluespice/_sf_instances/</code>
|
|-
|<code>$VOLUMES_DIR/bluespice/_sf_archive</code>
|<code>$DATADIR/wiki/bluespice/_sf_archive</code>
|
|}

===Settings===
{| class="wikitable"
!OLD (<code>bluespice/bluespice-pro</code> 4.4)
!NEW (<code>bluespice-deploy/composer</code> 4.5)
!Comment
|-
|<code>$VOLUMES_DIR/bluespice/LocalSettings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Fill in .env wiht relevant data. LocalSettings.php is not longer in use
Custom settings must be split up and added to those new files manually.
|-
|<code>$VOLUMES_DIR/bluespice/settings.php</code>
|
*<code>$DATADIR/bluespice/pre-init-settings.php</code>
*<code>$DATADIR/bluespice/post-init-settings.php</code>
|Custom settings must be split up and added to those new files manually.
|}

Setup:Installation Guide/Docker/Migration 4.4 to 4.5

2024-07-23T07:50:09Z

Fspinar:

SocialEntity:412

2022-06-20T08:50:53Z

Fspinar:

{
"wikipageid": 2058,
"namespace": 0,
"titletext": "Translationtranfer 3",
"description": "",
"parentid": 0,
"id": 412,
"ownerid": 12,
"type": "wikipage",
"archived": false,
"tags": [
"Translationtranfer 3"
],
"resolved": false
}

File:Raspberry pi.pdf

2022-06-09T06:32:34Z

Fspinar:

SocialEntity:404

2022-06-05T08:07:14Z

Fspinar:

{
"wikipageid": 2044,
"namespace": 0,
"titletext": "Translationtranfer II",
"description": "",
"parentid": 0,
"id": 404,
"ownerid": 12,
"type": "wikipage",
"archived": false,
"tags": [
"Translationtranfer II"
],
"resolved": false
}

SocialEntity:321

2022-03-24T10:18:32Z

Fspinar:

{
"wikipageid": 1700,
"namespace": 0,
"titletext": "Translationtest",
"description": "",
"parentid": 0,
"id": 321,
"ownerid": 12,
"type": "wikipage",
"archived": false,
"tags": [
"Translationtest"
],
"resolved": false
}

SocialEntity:318

2022-03-24T03:42:38Z

Fspinar:

{
"wikipageid": 1694,
"namespace": 0,
"titletext": "Manual:Extension/BlueSpiceTranslationTransfer",
"description": "",
"parentid": 0,
"id": 318,
"ownerid": 12,
"type": "wikipage",
"archived": false,
"tags": [
"Manual:Extension/BlueSpiceTranslationTransfer"
],
"resolved": false
}

Manual:Extension/BlueSpiceTranslationTransfer

2022-03-24T03:42:37Z

Fspinar: Created page with "BlueSpiceTranslationTransfer allows to create a translated Version of an Article in another Wiki"

BlueSpiceTranslationTransfer allows to create a translated Version of an Article in another Wiki

User:Fspinar

2022-01-20T08:24:08Z

Fspinar: create user page