Skip to main content
Upgrading ipmideck replaces the application, not your data. Your config.yaml, database, and encryption key live in the data directory, which stays put across an upgrade, so your servers, history, and settings carry over.

​
Docker

Pull the new image and recreate the container with the same data volume:
The -v ipmideck-data:/data volume holds your data, so reusing the same volume name keeps everything. Pin a version instead of latest (for example devluigi06/ipmideck:2.0.0) if you want to control exactly when you move between releases.

​
pipx

If you installed with pipx, which is the recommended path on Debian and Ubuntu, upgrade with:

​
pip

Upgrade the package in place, then start ipmideck again:
The -U flag matters, a plain pip install ipmideck does nothing when the package is already installed and leaves you on the old version.
The data directory is independent of the package, so the upgrade does not touch your config or database.

​
Check your version

The running version shows in the dashboard, and the console prints it in the credits line under the banner (for example v2.0.0). You can also read it from the health endpoint:
Take a backup before a major upgrade. Restoring is then a matter of putting the data directory back if anything goes wrong.

​
Next steps