Skip to content
GridNMS Docs

Updates

Collector updates

Section titled “Collector updates”

Collector updates are pushed automatically from the control plane over the existing tunnel — nothing to do. New collector software is delivered to connected collectors as part of normal check-in.

Server / UI updates

Section titled “Server / UI updates”

Server and UI updates are delivered by the updater service. When GridNMS publishes a new server release, your next hourly check-in records the target; the updater then:

  1. Pulls the published image from images.gridnms.io,
  2. Loads it and recreates the server container (which carries both the API and the UI),
  3. Health-checks the new container, and
  4. Auto-reverts to the prior image if the new one fails to come up.

There is no rebuild step.

Enable the updater

Section titled “Enable the updater”

Set the read-only update credentials in .env:

R2_ENDPOINT=...
R2_ACCESS_KEY_ID=...
R2_SECRET_ACCESS_KEY=...

Pin a version instead

Section titled “Pin a version instead”

Leave the R2_* values blank to pin your current version and update manually.