Proxmox Custom Scripts

Community-scripts-compatible Proxmox VE helper scripts for applications not found in the main community-scripts collection.

Website: https://oraad.github.io/proxmox-scripts/

Browse the catalog for install commands, resource defaults, and per-script notes.

What is this?

One-command LXC installations for self-hosted applications missing from community-scripts. Paste a command into your Proxmox shell, answer a few prompts, and the container is ready.

Current scripts:

• Music Assistant — Docker server with host networking
• HA MCP — ha-mcp HTTP endpoint for Cursor and other MCP clients
• NetAlertX — network visibility via Docker with host networking (privileged LXC)
• Pangolin Newt — dedicated LXC for the Pangolin tunnel agent
• Pangolin Newt Addon — install Newt on the Proxmox host or an existing LXC
• Pangolin CLI Addon — install the Pangolin machine VPN client on the host or an existing LXC
• PVE LXC Apps Updater — batch-update community-scripts and custom LXCs

Getting started

1. Go to oraad.github.io/proxmox-scripts
2. Open the script you want and copy the one-line install command
3. Run it on your Proxmox host (not inside a VM or container)
4. Choose Default or Advanced in the wizard and follow the prompts

Quick example (Music Assistant)

bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/ct/musicassistant.sh)"

Alpine LXC:

var_os=alpine var_version=3.23 bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/ct/musicassistant.sh)"

Per-script install details, ports, warnings, and troubleshooting live on each script page in the catalog (json/<slug>.json powers the site).

How scripts work

Default mode — Sensible resource defaults with minimal prompts.

Advanced mode — Full control over container settings before install.

After installation, each container includes an update command (also via pct exec <CTID> -- update from the host) to pull the latest application version.

Batch update (community-scripts + custom)

On the Proxmox host, update all tagged helper-script LXCs in one pass — including apps from this repo (musicassistant, ha-mcp, newt) and from community-scripts. The tool reads each container’s /usr/bin/update URL and loads ct/<service>.sh from the matching repository.

Interactive:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/tools/pve/update-apps.sh)"

Unattended (all running containers):

var_backup=no var_container=all_running var_unattended=yes var_skip_confirm=yes \
  bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/tools/pve/update-apps.sh)"

Repository layout

ct/                 Host-side LXC creation scripts
install/            In-container install scripts
defaults/           App-specific wizard defaults
json/               Script metadata for the website (per-script docs)
misc/build.func     Wrapper around upstream community-scripts build.func
tools/pve/          Host-side Proxmox tools (update-apps)
tools/addon/        Add-ons for the Proxmox host or existing LXCs
frontend/           GitHub Pages catalog (Next.js static export)

Adding a new script

1. Add ct/<app>.sh and install/<app>-install.sh
2. Add json/<app>.json metadata — description, notes, links (see json/musicassistant.json)
3. Optionally add defaults/<app>.vars and ct/headers/<app>
4. Push to main — GitHub Actions rebuilds the site automatically

Configuration

Repo URLs are set for oraad/proxmox-scripts in misc/build.func, ct/*.sh, install/*-install.sh, tools/pve/update-apps.sh, and frontend/src/config/site-config.ts.

GitHub Pages

Enable Settings → Pages → Build and deployment → GitHub Actions after pushing to GitHub.

License

MIT — see LICENSE.