Installing

Every component is an ordinary GLPI plugin. There is no installer, no patch to core, and nothing to reapply after a GLPI upgrade.

Requirements

GLPI	11.0 for everything except the command palette and presence, which install on 10.0
PHP	Whatever your GLPI requires — nothing here raises the floor
Composer	Not needed. No component adds anything to GLPI’s vendor tree
Licence	GPL-3.0-or-later

Three components want something outside GLPI, and say so on their own page: Search needs a Meilisearch server, osquery Inventory needs GLPI served over HTTPS, and Entitle reads an ERPNext instance running the glpi_billing app.

The plugin key is not the repository name

This is the one that costs an hour. GLPI identifies a plugin by the name of its directory under plugins/, and for most of the suite that differs from the repository it is cloned from: glpi-change installs as glpichange, glpi-whitelabel installs as whitelabel.

Clone into the wrong directory name and the plugin simply does not appear in Setup → Plugins — there is no error to read.

# from the GLPI root
git clone https://github.com/bijstaan/glpi-change.git plugins/glpichange
php bin/console plugin:install -u glpi glpichange
php bin/console plugin:activate glpichange

Every key is listed on Versions & requirements, and on each component’s own page.

Rights

Plugins that add their own objects add their own rights, and they start denied. After activating one, grant its rights in Administration → Profiles to the profiles that should have it; a plugin whose page is missing for a technician is nearly always a profile that was never granted its rights rather than a broken install.

Automatic actions

Several components do their real work on a cron: the vulnerability feeds, the nightly report rollups, the cloud sweep, the known-error clusterer, the SNMP scan schedule. GLPI’s own Setup → Automatic actions lists them once the plugin is active. An instance running GLPI’s cron from the web rather than from the system crontab will run them, but late and unevenly.

Removing one

php bin/console plugin:deactivate glpichange
php bin/console plugin:uninstall glpichange

Uninstalling drops the component’s own tables. It does not touch core’s — a project’s task dependencies, for instance, live in GLPI’s glpi_projecttasklinks rather than in a copy of it, so they survive the plugin that wrote them.