Docs

Install and operate

Upgrade and roll back

Each Lagoria Control image installs exactly its own version. To move to another version, you run that version's image. Your data stays where it is.

Upgrade#

  1. Read the release notes for the new version. They say whether it can be rolled back.
  2. Get the new image (docker pull, or docker load for the offline file).
  3. Start it with the same working folder as before, so your settings carry over.
  4. Connect AWS access, then open Deploy. The plan reads Upgrade 1.0.0 → 1.1.0.
  5. Choose Upgrade and confirm.
The upgrade plan, shown before anything changes.

Before the upgrade changes anything, Lagoria Control backs up every DynamoDB table. An upgrade usually takes a few minutes, since most resources already exist.

What Lagoria Control allows#

The installed version and a rollback floor are stored in your account. Lagoria Control compares them with the image's version and decides what it may do:

Installed vs. imagePlan
Nothing installedInstall
Image is newerUpgrade. Refused if the installed version is older than the image supports; the message names the version to upgrade to first.
Same versionReinstall. Useful after changing settings.
Image is olderRoll back. Refused if a later release changed data in a way this version cannot read.

Roll back#

  1. Start the previous image with the same working folder.
  2. Open Deploy. The plan reads Roll back 1.1.0 → 1.0.0.
  3. Confirm. The tables are backed up first, as for an upgrade.
Not every release can be rolled back

A release that changes stored data in a way older versions cannot read is marked not rollback-safe in its release notes, and Lagoria Control refuses to go back past it. Contact us before such a rollback: it means restoring the backup taken before the upgrade.

Change settings#

To change a setting without changing version, edit it in Configuration, then run a reinstall from Deploy with the same image.