Mise à jour

Note

Comme pour tout processus de mise à jour, une sauvegarde des données doit être effectuée avant toute tentative :

  • sauvegarde de votre base de données ;

  • backup your config directory, especially for your GLPI key files (config/glpi.key, config/glpicrypt.key, config/oauth.pem, config/oauth.pub) which are randomly generated;

  • backup your files directory, it contains users and plugins generated files, like uploaded documents;

  • backup your marketplace and plugins directories.

Here are the steps to update GLPI:

  • Download latest GLPI version.

  • Ensure the target directory is empty and extract files there.

  • Restore the previously backed up config, files, marketplace and plugins directories.

  • Then open the GLPI instance URI in your browser, or (recommended) use the php bin/console db:update command line tool.

Avertissement

As soon as a new version of GLPI files is detected, you will not be able to use the application until the update process has been done.

Avertissement

Ne pas essayer de restaurer une sauvegarde sur une base de données non vide (par exemple, une base partiellement migrée pour quelque raison que ce soit).

S’assurer que la base est vide avant de restaurer la sauvegarde et tenter de mettre à jour, refaire en cas d’échec.

Note

Before GLPI 11.0, all the plugins were disabled during the update process.

Since GLPI 11.0, as soon as a new version of GLPI files is detected, the plugins execution is suspended. Their execution will be resumed after the update only in case of a minor/bugfixes update. Otherwise, you will have to do it manually using the php bin/console plugin:resume_execution command line tool or from the plugins administration page.

Note

You can use the php bin/console db:check command line tool before executing the update command. This will allow you to check the integrity of your database, and to identify changes to your database that could compromise the update.

Creative Commons License