mirror of https://github.com/Icinga/icinga2.git
416a1458c9
We are using a central DB-Cluster, therefor Icinga2 got a database on this remote cluster. We used the icinga DB user, created during the step before, to import the DB schema. For this, the additional GRANT options `ALTER` and `CREATE` where needed to install the schema successfully via: ```bash mysql -u icinga -p icinga < /usr/share/icinga2-ido-mysql/schema/mysql.sql ``` Someone may find this a security problem. But I see two benefits: * these GRANT options are only set for the icinga.* database * this setup allows to execute also all later UPGRADE commands as the database user `icinga` - and not as the DB Administrator. Two additional notes: * I also included a small warning about the used default DB password * sadly, I have no way to change this also in the provided mariadb-centos7.png image, so this is left unchanged at the moment |
||
|---|---|---|
| .. | ||
| images | ||
| .gitignore | ||
| 01-about.md | ||
| 02-installation.md | ||
| 03-monitoring-basics.md | ||
| 04-configuration.md | ||
| 05-service-monitoring.md | ||
| 06-distributed-monitoring.md | ||
| 07-agent-based-monitoring.md | ||
| 08-advanced-topics.md | ||
| 09-object-types.md | ||
| 10-icinga-template-library.md | ||
| 11-cli-commands.md | ||
| 12-icinga2-api.md | ||
| 13-addons.md | ||
| 14-features.md | ||
| 15-troubleshooting.md | ||
| 16-upgrading-icinga-2.md | ||
| 17-language-reference.md | ||
| 18-library-reference.md | ||
| 19-technical-concepts.md | ||
| 20-script-debugger.md | ||
| 21-development.md | ||
| 22-selinux.md | ||
| 23-migrating-from-icinga-1x.md | ||
| 24-appendix.md | ||
| CMakeLists.txt | ||
| icinga2.8 | ||
| scroll.js | ||
| update-links.py | ||
| win-dev.ps1 | ||