Difference between revisions of "Setup:Installation Guide/Advanced/Configuration Folder settings.d"

Tag: 2017 source edit
Tag: 2017 source edit
 
Line 1: Line 1:
 +
{{Messagebox|boxtype=Hinweis|Note text=This document provides background information for advanced users. We recommend not to make any changes on BlueSpice, if you are not familiar with the following information.}}
  
 
*For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
 
*For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
 
*The placeholder <code>&lt;installpath-bluespice&gt;</code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).
 
*The placeholder <code>&lt;installpath-bluespice&gt;</code> stands for the path to your BlueSpice installation, e.g <code>C:\inetpub\wwwroot\bluespice</code> (Windows) or <code>/var/www/bluespice</code> (Linux).
{{Messagebox|boxtype=Hinweis|Note text=This document provides background information for advanced users. We recommend not to make any changes on BlueSpice, if you are not familiar with the following information.}}
+
 
 
==Explanation For the Folder settings.d==
 
==Explanation For the Folder settings.d==
 
<span lang="en" id="result_box" class=""><span class="">Starting with BlueSpice version 2.27.1, all default settings as well as the modules of BlueSpice are outsourced.</span></span> <span class="">All configurations can now be found in separate files in the /settings.d folder.</span>
 
<span lang="en" id="result_box" class=""><span class="">Starting with BlueSpice version 2.27.1, all default settings as well as the modules of BlueSpice are outsourced.</span></span> <span class="">All configurations can now be found in separate files in the /settings.d folder.</span>

Latest revision as of 15:52, 22 December 2021

Hinweis:This document provides background information for advanced users. We recommend not to make any changes on BlueSpice, if you are not familiar with the following information.


  • For editing the configuration files with a text editor, the files must be saved in UTF-8 coding without BOM (Byte Order Mark).
  • The placeholder <installpath-bluespice> stands for the path to your BlueSpice installation, e.g C:\inetpub\wwwroot\bluespice (Windows) or /var/www/bluespice (Linux).

Explanation For the Folder settings.d[edit | edit source]

Starting with BlueSpice version 2.27.1, all default settings as well as the modules of BlueSpice are outsourced. All configurations can now be found in separate files in the /settings.d folder.

The files in this folder integrate the standard MediaWiki extensions required for BlueSpice, perform recommended default configurations, and also integrate all BlueSpice-related extensions (free or pro).

The files in the /settings.d folder are automatically integrated in alphabetical order and are therefore prefixed with numbers.

If you want to add additional configurations yourself, you can save your own files here. For this, it is recommended to use the prefix 001-.

Additional configurations, which are not packed per default but can be used, can be found at auf github.com.

Update-safe changing of default configuration files[edit | edit source]

If you want to change the files delivered by default in the settings.d folder, we strongly recommend that you choose the following method so as not to lose this configuration after an update:

  • Create a copy of the respective configuration file with the extension .local.php - e.g. 020-VisualEditor.local.php
  • Only edit this file

Files with this file extension are generally preferred in the loading process.

No categories assignedEdit

Discussions