Andy Grunwald
f5390ebdbf
* Install Java via setup_java instead of distro openjdk Apache Tika's Java runtime was installed by calling apt directly for openjdk-17-jre-headless. This tied the JDK to whatever Debian ships, and that coupling has now broken: openjdk-17 is no longer available on Debian 13 (Trixie), where openjdk-21 is current. It also made this the only script in install/ that installs Java by hand, while every other Java application in the repository uses the shared setup_java helper. Switch to setup_java, which installs Eclipse Temurin from the Adoptium repository. Temurin is versioned independently of the Debian release, so a future distribution upgrade cannot remove the JDK out from under the application the way this one did. Java 21 satisfies both current and upcoming Tika: 3.x requires Java 11 or newer, and 4.x raises the floor to Java 17. The surrounding msg_info/msg_ok pair is dropped because setup_java emits its own progress messages; keeping them would nest the output. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Bump Apache-Tika container to Debian 13 The container declared Debian 12 (Bookworm) as its base, which had become an outlier: 475 of the repository's ct scripts target Debian 13 and only 22 still target 12. build.func also sets trixie as the default ARM64 template codename, so this script's declared base had drifted away from the repository default. The declared version is not cosmetic. check_container_os_guard() reads var_os/var_version as the script's recommended OS and compares them against a container's /etc/os-release, prompting on interactive runs and aborting headless ones when they disagree. Debian 12 was also the reason the previous openjdk-17 dependency looked valid; on Debian 13 that package no longer exists, which is addressed in the preceding commit. Existing Debian 12 containers keep working, because update_script only replaces the Tika jar and never touches the operating system or Java. They will, however, now hit the OS mismatch guard on update and be asked to move to Debian 13 first. That is intended rather than a regression, but it is a visible change for existing users. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Proxmox VE Helper-Scripts
One-command installations for services, containers, and VMs on Proxmox VE
A community project — built on the foundation of @tteck's original work
What is this?
Simplify your Proxmox VE setup with community-driven automation scripts.
Install and configure popular self-hosted services with a single command — no manual package hunting, no config file archaeology. Paste a command into your Proxmox shell, answer a few prompts, and your container or VM is up and running.
The collection covers hundreds of services across categories like home automation, media servers, networking tools, databases, monitoring stacks, and more.
Requirements
| Component | Details |
|---|---|
| Proxmox VE | Version 8.4, 9.0, 9.1, or 9.2 |
| Host OS | Proxmox VE (Debian-based) |
| Access | Root shell access on the Proxmox host |
| Network | Internet connection required during installation |
Getting Started
The fastest way to find and run scripts:
- Go to community-scripts.org
- Search for the service you want (e.g. "Home Assistant", "Nginx Proxy Manager", "Jellyfin")
- Copy the one-line install command from the script page
- Open your Proxmox Shell and paste it
- Choose between Default or Advanced setup and follow the prompts
Each script page documents what the container includes, default resource allocation, and post-install notes.
How Scripts Work
Every script follows the same pattern:
Default mode — Picks sensible resource defaults (CPU, RAM, storage) and asks only the minimum required questions. Most installs finish in under five minutes.
Advanced mode — Gives you full control over container settings, networking, storage backends, and application-level configuration before anything is installed.
After installation, each container ships with a post-install helper accessible from the Proxmox shell. It handles common tasks like:
- Applying updates to the installed service
- Changing application settings without manually editing config files
- Basic troubleshooting and log access
What's Included
The repository covers a wide range of categories. A few examples:
| Category | Examples |
|---|---|
| Home Automation | Home Assistant, Zigbee2MQTT, ESPHome, Node-RED |
| Media | Jellyfin, Plex, Radarr, Sonarr, Immich |
| Networking | AdGuard Home, Nginx Proxy Manager, Pi-hole, Traefik |
| Monitoring | Grafana, Prometheus, Uptime Kuma, Netdata |
| Databases | PostgreSQL, MariaDB, Redis, InfluxDB |
| Security | Vaultwarden, CrowdSec, Authentik |
| Dev & Tools | Gitea, Portainer, VS Code Server, n8n |
Browse the full list at community-scripts.org/categories — new scripts are added regularly.
Contributing
This project runs on community contributions. Whether you want to write new scripts, improve existing ones, or just report a bug — every bit helps.
Where to start
| I want to… | Go here |
|---|---|
| Add a new script | ProxmoxVED — new scripts are tested here first |
| Fix or improve an existing script | Contributing Guidelines — open a PR in this repo |
| Report a bug or broken script | Issues |
| Request a new script or feature | Discussions |
| Report a security vulnerability | Security Policy |
| Get help or chat with other users | Discord |
Before you open a PR
- New scripts go to ProxmoxVED, not here. PRs with new scripts opened directly against this repo will be closed.
- Bug fixes and improvements to existing scripts belong in this repo — read the Contributing Guidelines first.
- Keep PRs focused. One fix or feature per PR.
- Document what your script installs and any non-obvious decisions in the corresponding JSON metadata file.
Core Team
 MickLesk |
 michelroegl-brunner |
 BramSuurdje |
 CrazyWolf13 |
 tremor021 |
 vhsdream |
 asylumexp |
Project Activity
Support the Project
This project is maintained by volunteers. All infrastructure costs come out of pocket, and the work is done in people's spare time.
30% of all donations are forwarded directly to cancer research and hospice care — a cause that was important to tteck.
License
This project is licensed under the MIT License — free to use, modify, and redistribute for personal and commercial purposes.
See the full license text in LICENSE.
Maintained and expanded by the community · In memory of tteck
Proxmox® is a registered trademark of Proxmox Server Solutions GmbH