7715a02f05
* Simplify Alpine update scripts to run upgrade Remove interactive whiptail menus, loops and newt dependency checks from ct/alpine-docker.sh, ct/alpine-zigbee2mqtt.sh, and ct/alpine.sh. Each update_script now simply calls header_info, runs $STD apk -U upgrade, displays a success message and exits, simplifying and automating the update flow. * feat(update-scripts): replace whiptail with msg_menu for unattended updates Remove all whiptail dialogs from ct update_script() functions and replace with msg_menu() - a lightweight read-based menu that supports: - PHS_SILENT=1: auto-selects first (default) option for unattended mode - Interactive: numbered menu with 10s timeout and default fallback Converted scripts (whiptail menu → msg_menu): - plex.sh, npmplus.sh, cronicle.sh, meilisearch.sh, node-red.sh - homeassistant.sh, podman-homeassistant.sh - vaultwarden.sh, alpine-vaultwarden.sh - loki.sh, alpine-loki.sh - alpine-grafana.sh, alpine-redis.sh, alpine-valkey.sh - alpine-nextcloud.sh Simplified scripts (removed unnecessary whiptail for single-action updates): - alpine.sh, alpine-docker.sh, alpine-zigbee2mqtt.sh Special handling: - gitea-mirror.sh: replaced yesno/msgbox with read -rp confirmations, exit 75 in silent mode for major version upgrades requiring interaction - vaultwarden.sh/alpine-vaultwarden.sh: passwordbox replaced with read -r -s -p, skipped in silent mode with warning - nginxproxymanager.sh: exit 1 → exit 75 for disabled script Infrastructure: - Added msg_menu() helper to misc/build.func - Added exit code 75 handling in update-apps.sh (skip, not fail) Closes #11620 * refactor(update-scripts): remove menus where sequential updates suffice - alpine-nextcloud: add apk upgrade as the update action (was missing) - meilisearch: run meilisearch + UI updates sequentially (like bar-assistant) - npmplus: run alpine upgrade + docker pull sequentially, no menu - vaultwarden: update VaultWarden + Web-Vault sequentially, remove admin token option (interactive-only, not suitable for unattended updates) - alpine-vaultwarden: just run apk upgrade, remove admin token menu
Proxmox VE Helper-Scripts
A Community Legacy in Memory of @tteck
Simplify your Proxmox VE setup with community-driven automation scripts
Originally created by tteck, now maintained and expanded by the community
🎯 Key Features
⚡ Quick SetupOne-command installations for popular services and containers |
⚙️ Flexible ConfigSimple mode for beginners, advanced options for power users |
🔄 Auto UpdatesKeep your installations current with built-in update mechanisms |
🛠️ Easy ManagementPost-install scripts for configuration and troubleshooting |
👥 Community DrivenActively maintained with contributions from users worldwide |
📖 Well DocumentedComprehensive guides and community support |
🔒 SecureRegular security updates and best practices |
⚡ PerformanceOptimized configurations for best performance |
📋 Requirements
🖥️ Proxmox VEVersion: 8.4.x | 9.0.x | 9.1.x |
🐧 Operating SystemDebian-based with Proxmox Tools |
🌐 NetworkInternet connection required |
📥 Getting Started
Choose your preferred installation method:
Method 1: One-Click Web Installer
The fastest way to get started:
- Visit helper-scripts.com 🌐
- Search for your desired script (e.g., "Home Assistant", "Docker")
- Copy the bash command displayed on the script page
- Open your Proxmox Shell and paste the command
- Press Enter and follow the interactive prompts
Method 2: PVEScripts-Local
Install a convenient script manager directly in your Proxmox UI:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pve-scripts-local.sh)"
This adds a menu to your Proxmox interface for easy script access without visiting the website.
📖 Learn more: ProxmoxVE-Local Repository
💬 Join the Community
💬 DiscordReal-time chat, support, and discussions 
|
💭 DiscussionsFeature requests, Q&A, and ideas 
|
🐛 IssuesBug reports and issue tracking 
|
🛠️ Contribute
💻 CodeAdd new scripts or improve existing ones |
📝 DocumentationWrite guides, improve READMEs, translate content |
🧪 TestingTest scripts and report compatibility issues |
💡 IdeasSuggest features or workflow improvements |
👉 Check our Contributing Guidelines to get started
❤️ Support the Project
This project is maintained by volunteers in memory of tteck. Your support helps us maintain infrastructure, improve documentation, and give back to important causes.
🎗️ 30% of all donations go directly to cancer research and hospice care
Every contribution helps keep this project alive and supports meaningful causes
📈 Project Statistics
📜 License
This project is licensed under the MIT License - feel free to use, modify, and distribute.
Proxmox® is a registered trademark of Proxmox Server Solutions GmbH