Install with the Installer

The installer is a small bootstrap script published with every release. It downloads the release, proves it is intact, and hands the installation to Row-Template’s own management library, which does the rest as one transaction.

Run it

As root, on the server that runs your panel:

bash <(curl -fsSL https://github.com/iitzSeriZdev/Row-Template/releases/latest/download/install.sh)

releases/latest/download always resolves to the newest stable release (never a draft or pre-release), over HTTPS, with no token.

Run it from a root shell

Open one with sudo -i first. sudo bash <(curl …) fails because sudo closes the file descriptor that <(…) hands to bash.

What happens, in order

The bootstrap checks and downloads

It refuses to run unless it is root, and unless tar and sha256sum (or shasum) are present. It then downloads manifest.txt, SHA256SUMS and the release tarball named in the manifest.

The checksum is verified — always

The tarball’s SHA-256 must match the value in SHA256SUMS. There is no option, flag or environment variable that skips this. On a mismatch the installer stops before anything is extracted.

The archive is screened, then extracted

Every entry is checked before extraction: absolute paths, .. traversal, symlinks, hard links and special files are refused. Extraction never keeps the archive’s owners or permissions.

The library takes over and finds your panel

The extracted management library re-checks the payload (the page’s checksum, its structure, and that every installer file it declares is present), then decides which panel to install for:

an existing installation keeps the panel it was installed for;
otherwise RT_PANEL, if set, must name a panel installed on this server;
otherwise the one supported panel on the server — and with several, an interactive install asks, while a scripted one stops before changing anything.

It then checks that panel can be served: 3X-UI must be 3.6.0 or newer with a readable version, and Rebecca must be the 1.x Go edition — its 0.0.x Docker image is refused here. Nothing has been changed yet.

Files are installed

The install tree is created — /etc/3x-ui/sub_templates/row-template on 3X-UI, /etc/row-template on PasarGuard and Rebecca. VERSION, a record of the panel it serves, the management library and its components are installed there, and the row-template command at /usr/local/bin/row-template. Every file is written to a temporary name and renamed into place, so nothing is ever half-written.

Every design is verified

All seventeen designs are copied into the install’s template store — each in the version built for your panel’s template engine — and every one is checked against its own checksum and validated first.

You choose a design and your branding

On a first, interactive install you get the design chooser and the branding questions (below). A repair keeps your existing configuration.

The page is generated and swapped in

The live page sub.html is generated from the chosen design and your branding, validated, and only then moved into place.

The panel is pointed at it

3X-UI: when sqlite3 is available, the installer can set the panel’s subThemeDir for you (it asks first on an interactive install). Otherwise it prints the one manual step.
PasarGuard: the page is placed in PasarGuard’s templates directory, a marked block selecting it is appended to /opt/pasarguard/.env, and a running panel is restarted once.
Rebecca: the page is placed in Rebecca’s templates directory and selected in its subscription settings — automatically with SQLite and sqlite3, otherwise by you in the dashboard.

On PasarGuard and Rebecca this runs as a transaction: the panel’s settings are snapshotted, changed and verified, and restored exactly if any step fails. See Activation.

A live check runs

Finally it checks what the panel really serves. On 3X-UI, when it can find a subscription to test with (this needs sqlite3 and the panel database), it requests your subscription endpoint as a browser would and as a VPN app would, and reports what each received. On PasarGuard and Rebecca it asks the running panel which page it uses.

The questions it asks

An interactive install — a terminal on both ends — asks these in order. Every default is safe: pressing Enter all the way through gives you Row, no branding, and automatic activation where possible.

Prompt	What to enter
`More than one panel is installed on this host`, then a numbered list	Only on a server with several supported panels: the number of the panel Row-Template should serve.
`Continue installation? [Y/n]`	Enter to continue. Shown with the panel it detected (and, on 3X-UI, its version).
`Choose your Row-Template design` then `Select [1-17, Enter=Row]`	A number from the list, or Enter for Row. Preview the designs.
`Use them for this page? [Y/n]`	PasarGuard and Rebecca, when the panel’s own subscription settings hold a title or a support link (shown above the question): Enter to use them and skip the next two questions, `n` to type your own.
`Service name (Enter to keep, - to clear)`	The name your subscribers should see, up to 120 characters. Empty is fine: the page stays unbranded.
`Support URL, optional (Enter to keep, - to clear)`	A link starting with `https://`, `http://`, `tg://` or `mailto:`. Anything else is refused and asked again.
`Logo file [none] (Enter to keep, - to remove, or a path)`	Path to a PNG, JPEG or WebP file of at most 256 KiB, or Enter for the generated monogram.
`Install with these settings? [Y/n]`	Enter to install. Answer `n` to go back and change the branding.
`Make Row-Template the active 3X-UI subscription theme now? [Y/n]`	3X-UI: Enter to let the installer set `subThemeDir`. Only shown when `sqlite3` and the panel database are available.
`Make Row-Template the active PasarGuard subscription page now? [Y/n]` (or `… Rebecca …`)	PasarGuard and Rebecca: shown after a short description of what activation changes. Enter to activate; `n` leaves it for later, from the manager.

After you enter a service name, the installer shows a monogram preview — the letters used in place of a logo — for plain Latin names. For other scripts it notes that the browser computes the monogram.

When it finishes you get a summary: service, version, panel, template, install directory, and whether the page is Active, needs manual activation, or was not activated yet.

Running it again

Running the installer on a server that already has Row-Template does not reinstall blindly, and it always keeps the panel the installation serves. Interactively, it offers:

  1  Open the manager
  2  Reconfigure branding
  3  Update
  4  Repair / Verify
  0  Exit

Repair re-installs the release’s files in place. A backup of the current install is taken first, and your branding and design are kept.

Without a terminal on standard input (for example from a script), an existing install is only repaired when you say so explicitly:

RT_ASSUME_YES=1 bash <(curl -fsSL https://github.com/iitzSeriZdev/Row-Template/releases/latest/download/install.sh)

One installation serves one panel. To serve a different panel on the same server, run row-template uninstall first.

Unattended install

For provisioning scripts, give every answer through the environment. RT_ASSUME_NONINTERACTIVE=1 turns off all prompts; the panel is then activated automatically when it can be.

RT_ASSUME_NONINTERACTIVE=1 \
RT_TEMPLATE=editorial \
RT_SERVICE_NAME="Aurora VPN" \
RT_SUPPORT_URL="https://t.me/aurora_support" \
RT_LOGO_PATH=/root/aurora-logo.png \
bash <(curl -fsSL https://github.com/iitzSeriZdev/Row-Template/releases/latest/download/install.sh)

More than one panel on the server?

A scripted fresh install on a server with more than one supported panel must name the panel — add RT_PANEL=3xui, RT_PANEL=pasarguard or RT_PANEL=rebecca. Without it the installer stops before changing anything.

An invalid value stops the install before the panel is changed. Every variable is described in Environment variables.

If something goes wrong

The installer stops at the first problem and says what it was. Nothing is activated until the new page has been generated and validated, so a failed run never leaves a broken page live. Look the message up in the error reference.