update V2

This commit is contained in:
David Schroeder
2026-08-12 23:01:19 -05:00
parent 72d61e5785
commit 1d50229a08
7 changed files with 29 additions and 14 deletions
+8 -7
View File
@@ -8,7 +8,7 @@ VE environments.
Run as `root` on a Proxmox VE host:
```bash
bash <(curl -fsSL https://tagit.technologyarch.com/TAI/TA-ProxMenu/raw/branch/V2/install-ta_proxmenu.sh)
bash <(curl -fsSL https://tagit.technologyarch.com/TAI/TA-ProxMenu/raw/branch/main/install-ta_proxmenu.sh)
```
The installed launcher loads TA-ProxMenu's bundled defaults and colors, then
@@ -22,9 +22,10 @@ branch, and fast-forward safety checks. Offline, unreachable, dirty, ahead, or
diverged nodes are never overwritten and are reported as failures. Standalone
hosts retain the local-only update behavior.
When testing this branch, use `tapm main` to switch the installed copy back to
the published main branch. The command refuses to switch when local changes,
local-only commits, or diverged branch history would be at risk.
Legacy installations automatically update from the published `main` branch.
On their first launch after receiving this version, control is handed to the
current preloader so the new startup configuration and registration procedures
run before the menu opens.
The TA-ProxMenu Management menu can safely switch TA-ProxMenu between branches published on
its Git origin. Branch switching is refused when the installed repository has
@@ -104,7 +105,7 @@ Pulse can also be deployed without installing TA-ProxMenu. Run the standalone
bootstrap as root on a Proxmox VE host:
```bash
bash <(curl -fsSL https://tagit.technologyarch.com/TAI/TA-ProxMenu/raw/branch/V2/install-pulse.sh)
bash <(curl -fsSL https://tagit.technologyarch.com/TAI/TA-ProxMenu/raw/branch/main/install-pulse.sh)
```
The bootstrap downloads the Pulse deployment module and its LXC storage helper
@@ -167,7 +168,7 @@ without `https://` or a path. Repository updates use the installed
TA-ProxMenu checkout's configured Git `origin` and do not overwrite the system
configuration file.
On the first V2 launch after installation or upgrade, TA-ProxMenu detects a
On the first launch after installation or upgrade, TA-ProxMenu detects a
missing or incomplete `/etc/ta-proxmenu/config.env` and interactively requests
both values. Inputs are validated and written atomically with mode `0600`
before update checks or menu actions continue. A non-interactive launch without
@@ -176,7 +177,7 @@ a default company URL.
## Installation registry
V2 creates a random installation UUID and 256-bit credential in
TA-ProxMenu creates a random installation UUID and 256-bit credential in
`/var/lib/ta-proxmenu/identity.env`. The directory is mode `0700` and the file
is mode `0600`. The first successful launch enrolls the host with the broker.
Later launches make one best-effort HTTPS call on completion or failure to