tyler.durden/icingaweb2
1
0
Fork 0
mirror of https://github.com/Icinga/icingaweb2.git synced 2025-07-23 05:44:36 +02:00
Code Issues Packages Projects Releases Wiki Activity

Document that the instances.ini has been renamed

Browse Source 
refs #9651
This commit is contained in:
Johannes Meyer 2015-08-27 15:34:09 +02:00
parent 8c887ee450
commit 2829ecc8b7
1 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/installation.md
View File

@ -275,9 +275,11 @@ The first release candidate of Icinga Web 2 introduces the following non-backwar
`icingaweb_group_membership` were altered to ensure referential integrity. `icingaweb_group_membership` were altered to ensure referential integrity.
Please use the upgrade script located in **etc/schema/** to update your Please use the upgrade script located in **etc/schema/** to update your
database schema database schema
* Users who are using PostgreSQL < v9.1 are required to upgrade their * Users who are using PostgreSQL < v9.1 are required to upgrade their
environment to v9.1+ as this is the new minimum required version environment to v9.1+ as this is the new minimum required version
for utilizing PostgreSQL as database backend for utilizing PostgreSQL as database backend
* The restrictions `monitoring/hosts/filter` and `monitoring/services/filter` * The restrictions `monitoring/hosts/filter` and `monitoring/services/filter`
provided by the monitoring module were merged together. The new provided by the monitoring module were merged together. The new
restriction is called `monitoring/filter/objects` and supports only a restriction is called `monitoring/filter/objects` and supports only a
@ -296,3 +298,7 @@ for each installed module in the format `module/<moduleName>`. Administrators ha
users and/or user groups in the roles configuration for permitting access to specific modules. users and/or user groups in the roles configuration for permitting access to specific modules.
In addition, restrictions provided by modules are now configurable for each installed module too. Before, In addition, restrictions provided by modules are now configurable for each installed module too. Before,
a module had to be enabled before having the possibility to configure restrictions. a module had to be enabled before having the possibility to configure restrictions.
* The **instances.ini** configuration file provided by the monitoring module
has been renamed to **commandtransports.ini**. The content and location of
the file remains unchanged.