External Repositories
External Repositories~3 min
ProxMenux integrates with selected external script repositories as alternative options in some menu sections. These scripts come from trusted third-party sources and are clearly labelled with their origin when shown in the menu.
What this means in practice
When a menu option is backed by an external script (rather than ProxMenux's own code), the menu explicitly says where it's from and which repository it loads. ProxMenux acts as a launcher — it doesn't modify the external scripts. Issues with what an external script does belong to that repository's maintainer, not to ProxMenux.
Currently integrated
Attribution & recognition
- Credit is always given to the original authors in the menu and in the documentation page that wraps the script.
- A link to the source repository is shown — both before running the script and on the matching docs page.
- Users are encouraged to support the developers of these external projects (give a ⭐, sponsor, file quality bug reports).
Where to report problems with external scripts
If a script from one of these external repositories doesn't work as expected, report it directly to that repository — not to ProxMenux. ProxMenux just downloads and runs the script verbatim; it doesn't modify the source. The original maintainer is the right person to triage and fix it. ProxMenux issues are for problems with the launcher itself or with how ProxMenux integrates the external script.
Suggesting new external repositories
Found a script or repository that would fit nicely into a ProxMenux menu? Suggest it via:
💬 Open a Discussion
Best for ideas — gets community input before becoming a feature request.
🐛 Open an Issue
For specific feature requests with a clear scope.
What makes a good integration candidate
- Open source with an active maintainer.
- Idempotent / safe to run more than once.
- Doesn't silently modify Proxmox core config.
- Solves a problem ProxMenux doesn't already cover (avoids feature duplication).