You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requires all nodes to be shut down during upgrade: 🟢 No / ⚠️ Yes (Update nzyme-node upgrade procedure below)
Breaking Changes
New migrate command must be executed after update.
Important Changes
The data retention configuration is now tenant-based and can be found on the "Database" page of each tenant. Before this, it was globally defined under "System". An automatic migration applies the previous global configuration to each tenant during upgrade.
New Optional Configuration Parameters
Upgrade Procedure
nzyme-node
If you are upgrading from a previous version, you can simply run dpkg -i on the new release
package, execute database migrations and restart the nzyme-node service. Always upgrade nzyme-node before nzyme-tap unless instructed otherwise:
If you are upgrading from a previous version, you can simply run dpkg -i on the new release
package and restart the nzyme-tap service. Always upgrade nzyme-node before nzyme-tap
unless instructed otherwise.
Version [version] Meta Release Ticket
nzyme-node
upgrade procedure below)Breaking Changes
migrate
command must be executed after update.Important Changes
New Optional Configuration Parameters
Upgrade Procedure
nzyme-node
If you are upgrading from a previous version, you can simply run
dpkg -i
on the new releasepackage, execute database migrations and restart the
nzyme-node
service. Always upgradenzyme-node
beforenzyme-tap
unless instructed otherwise:Debian-based systems:
nzyme-tap
If you are upgrading from a previous version, you can simply run
dpkg -i
on the new releasepackage and restart the
nzyme-tap
service. Always upgradenzyme-node
beforenzyme-tap
unless instructed otherwise.
Debian-based systems:
The text was updated successfully, but these errors were encountered: