Updating

row-template update

This downloads the latest stable release, verifies it, and applies it. Your branding, your chosen design and the panel your installation serves are kept.

The command always applies the latest release

row-template update does not compare versions: it re-applies the latest release even when you already run it, which makes it a dependable repair. The manager’s 1 — Update is the one that checks first and asks — see The interactive manager.

What happens

Download and verify

The release is fetched from GitHub (or from RT_RELEASE_DIR / RT_RELEASE_URL), its SHA-256 checked, and the archive screened and extracted — exactly as in a fresh install.

Check the new release

The new page is validated, every installer file the release declares must be present and match its checksum, and all of the release’s designs — in the version for your panel — are verified into the template store. Any problem stops the update here, before anything is changed.

Keep your design

Your current design is taken from the new release’s copy. If the new release no longer includes it, Row is used and you are warned.

Back up

A snapshot of the current installation is taken. If it cannot be, the update stops.

Stage and activate

The new page, VERSION, the management library, its components and the row-template command are installed, then the live page is regenerated from the new version with your branding, validated, and swapped in. On PasarGuard and Rebecca the copy in the panel’s templates directory is replaced too.

A successful update prints:

  Updating Row-Template 1.3.1 -> 1.4.0
  ok   Update complete: now running 1.4.0.

followed by the live checks. Old backups are then pruned to the two newest.

If activation fails

The previous version is restored from the snapshot automatically:

  FAIL activation of the new version failed; rolling back.
  warn rolled back to 1.3.1; no changes are live.

The command exits with status 1. Your subscribers keep seeing the previous page throughout. If the automatic restore also fails — which needs two independent failures — you are told to run row-template rollback.

Upgrading from 1.3.0 or 1.3.1

One row-template update, on any panel. Your design, branding and panel wiring are kept, and the 1.4.0 page is in place at once. To take the name and support link PasarGuard or Rebecca already holds, see Branding.

Upgrading from 1.1.0 or 1.2.0

The published upgrade paths from these releases, to 1.3.0 and to 1.4.0 alike, take one command:

row-template update

From 1.2.0, the 1.2.0 updater installs the new release completely: every design and every installer file.
From 1.1.0, the command you run is still 1.1.0’s, and its updater copies only part of the new release: the page updates and your branding is kept, but the designs and the installer’s companion files are not installed yet. The next time you open row-template, or run row-template config or row-template verify as root, the new release downloads the rest of that same release — every design, checksum-verified — before doing anything else:

  Completing the Row-Template 1.4.0 installation (designs and installer files)...
  ok   Installation completed: 17 design(s) available.

It never downloads a newer version this way, and leaves your page, branding, selected design and backups as they are. If the release cannot be reached, it says so and tries again the next time; row-template update also completes the installation.

Your design, branding and panel wiring are kept either way. An installation made before 1.3.0 is a 3X-UI installation — earlier releases did not install on PasarGuard or Rebecca, so on those panels you install the new release rather than update.

1.2.1

There was no public 1.2.1 release. The fixes prepared under that number — including the one-step upgrade from 1.1.0 above — are included in 1.3.0.

Updating without GitHub access

Point the update at a folder containing a release you downloaded and verified yourself:

RT_RELEASE_DIR=/root/row-template-X.Y.Z-release row-template update

See Manual installation.

What an update never changes

Your branding (config.env).
Your design, while the new release ships it.
The panel the installation serves, and the panel’s selection: on 3X-UI subThemeDir already points at the install directory, which does not move; on PasarGuard and Rebecca the placed page is replaced in place, the selection is not touched, and nothing is restarted.
Your existing backups, apart from pruning to the two newest valid ones.

To go back to the version you had before an update, use rollback.