TA-ProxMenu

Interactive installation and configuration helpers used when deploying Proxmox VE environments.

Install

Run as root on a Proxmox VE host:

bash <(curl -fsSL https://go.scity.us/install-tapm)

The installed launcher loads the shared iDSSYS defaults and opens the interactive menu. Update availability is checked in the background and cached; updates are installed only when explicitly selected or requested with tapm update.

The required iDSSYS Defaults repository is handled separately: it is automatically refreshed before launch when its last successful check is more than four hours old. If the remote is unavailable, the installed copy is used. Updates are fast-forward-only. Local file changes, local-only commits, and diverged histories are preserved and reported instead of being overwritten.

The Utilities menu can safely switch TA-ProxMenu between branches published on its Git origin. Branch switching is refused when the installed repository has local changes or when the destination branch has commits that would be discarded.

Direct actions

The menu script also supports these direct actions:

pulse        Install Pulse monitoring
rmm          Install the ConnectWise RMM agent
omsa         Install Dell OpenManage Server Administrator
glances      Install Glances
acronis      Install the Acronis agent
post-install Run the ProxMenux post-install configuration
proxmenux     Install or open ProxMenux
virtio       Download current VirtIO drivers
sentinelone  Install the SentinelOne agent
screenconnect Install the ScreenConnect agent
restart      Restart core local Proxmox management services
cpu          Detect and optionally apply a migration-safe CPU model
maintenance  Toggle local HA maintenance mode
keepalived   Deploy Keepalived across the cluster

Companion files

Large installer artifacts used by this project are stored in the private TAI/files package registry. SentinelOne, RMM, Acronis, and ScreenConnect installation require a temporary deployment code from TAPM Deployment Access. The private Gitea credentials are never stored on or returned to a Proxmox host. SentinelOne package versions can be updated through the deployment portal without changing ProxMenu.

Runtime requirements

Proxmox VE and root privileges
Bash, Git, curl, wget, Python 3, and standard Debian package tools
/opt/idssys/defaults/default.inc
/opt/idssys/defaults/colors.inc

The Keepalived deployment additionally requires a healthy, quorate Proxmox cluster and passwordless root SSH between cluster nodes.