Updating GLPI

This page covers how to update to a new GLPI release.

• Release notes on Github

Updating GLPI Network Cloud

---

If you're on a GLPI Network Cloud plan, we'll upgrade your GLPI automatically with each new release; no action needed on your end (unless you're using the GLPI Network Cloud Private offer – so you may ask the upgrade on demand)

How soon we upgrade your instance depends on the type of release:

• Security fixes: One week before the public release

• Minor releases (e.g., 10.0.18 to 10.0.19): Usually about a week

• Major releases (e.g., 10.0.20 to 11.0.0): Longer, usually months (just to make sure everything goes smoothly)

GLPI Network Cloud Private customers can request an update at support.teclib.com. Include the URL of the GLPI Network Cloud instance you want us to upgrade.

Updating a Self-Hosted GLPI

---

This page covers the updating process of an instance that was installed following this article. If your installation was made with different steps, please make sure to adapt commands and paths according to your environment.

Here are the steps for updating to a new GLPI version (major or minor):

1. Back up of your application database and files

The application database keeps track of everything of your GLPI instance. It is very unlikely you'll need to roll back to your current version, nevertheless it is always great to have a point of coming back in case something goes wrong.

Never try to import a GLPI database backup to a different version without using the update scripts contained here.

You should not try to restore a database backup on a non empty database (say, a database that has been partially migrated for any reason).

Make sure your database is empty before restoring your backup and try to update, and repeat on fail.

1. Download latest GLPI version

On http://glpi-project.org/download, find the latest version, and download it to your server, and extract it to an empty folder where your Web Server may find it.

wget https://github.com/glpi-project/glpi/releases/download/x.x.x/glpi-x.x.x.tgz

1. Ensure target directory is empty and extract files there

cd /var/www/html
tar -xzf glpi-x.x.x.tgz

1. Restore the downstream.php file previously backed up

This procedure follows the standard Filesystem Hierarchy Standard (FHS) to clearly separate critical elements: configuration files (including the encryption key), application sources, variable data, and logs.

This organization strengthens the security and maintainability of the instance. For more information, see the installation article.

cp ..glpibackup/inc/downstream.php /var/www/html/glpi/inc

1. Update GLPI

Open the GLPI Instance URL on your browser, or (recommended) use the php bin/console db:update command line tool

The command line tool will check the integrity of your database to identify changes that could compromise the update, and run migrations to update GLPI

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 finished.

1. Update and enable the plugins

Update process will automatically disable your plugins. So make sure to enable them again after updating them.

You find a video covering this process below: