Integrate ProxMenux administration script

[migueldeblas]

🌟 Briefly describe the feature

Integrate ProxMenux administration script

📝 Detailed description

There is a ProxMenux administration script that could be integrated into this set of scripts. It follows the same philosophy but performs complementary tasks.

https://github.com/MacRimi/ProxMenux

💡 Why is this useful?

It follows the same philosophy but performs complementary tasks.

[MickLesk]

#1452

but i dont know, how we can integrate this. its "useless" to bash call and script in our repo to use this. 😄
Our site can only evaluate scripts that are basically stored by us. In other words, I would have to make an addon .sh which calls his bash. It is possible, but it is simply inconvenient.

@MacRimi any idea?

[MacRimi]

Hi @MickLesk and @migueldeblas,

Thank you for your response. I completely understand your concerns regarding structure and script inclusion.

I’d like to clarify and expand on the original suggestion made by @migueldeblas, drawing on the conversations I’ve had with ProxMenux users (based on their feedback), as well as the proposal I previously shared in Discussion #1452.

I’d like to propose two possible forms of collaboration:

1. Integration of Proxmox VE Helper-Scripts within ProxMenux
   This would involve creating a dedicated submenu inside ProxMenux, listing all your scripts — properly categorized — and linking directly to the versions in your official repository.

After running each script, a message like the following would be displayed:

Visit the website to discover more scripts, stay updated with the latest updates, and support the project:

https://community-scripts.github.io/ProxmoxVE

This requires no changes on your side, but I’d love to do this with your official approval and suggestions, to make sure it aligns with the philosophy and visual style of the Helper-Scripts project originally initiated by @tteck.

2. Optional: Lightweight installer script for ProxMenux
   If you see value in listing ProxMenux as a complementary tool, I’d be happy to create a .sh script following your format that installs ProxMenux easily.

The latest version I’m working on includes a much lighter and cleaner installer, where the user can choose whether to enable translation features or not — making it easy to adapt to your standards and keep the integration simple.

Both projects share the same goal: making Proxmox more accessible and user-friendly for the community.
If you think this kind of collaboration could be helpful, I’d be happy to take the first step and send you a draft of the integration or installer script for review.

What do you think about the idea?

[MickLesk]

1. = fine by me.

2. Basically, this is not a problem as long as it roughly meets our requirements and does not deviate too far in terms of design.

Examples: tools\pve:

• clean-lxcs.sh
• lxc-delete.sh
• pve-privilege-converter

If you want to prepare something, feel free to push it to the DEV repo:
https://github.com/community-scripts/ProxmoxVED

[MacRimi]

I’ll take a closer look at the DEV repository this afternoon and start testing a few ideas to send over as a proposal.

Really appreciate the opportunity — I’ll keep it aligned with your format and design style.

Talk soon!

[migueldeblas]

My initial idea was for proxmenux to be one of the scripts in the helper script project. It would remain its authorship and be maintained by its author. Both projects are perfect, and unity is strength. I believe there should be no dispersion; a single site for a single purpose is ideal. Proxmox isn't as popular as many people think. But since its author has weighed in, I have nothing more to say. Thank you for considering it.

[MacRimi]

Thank you so much for bringing up the idea and for your thoughtful message!

In fact, the goal is exactly as you described: if we prepare a lightweight installer script in the Helper-Scripts format, ProxMenux could indeed be included as an option within the official repository — while still being maintained independently.

I truly appreciate your support and vision for unifying efforts to benefit the community. As you said: unity is strength. 💪

Thanks again!

[migueldeblas]

The only thing I see differently is the installation, which is precisely what you mentioned. I've reviewed the scripts that refer to maintenance and actions on Proxmox itself or the VMs or LXCs it contains, and I haven't seen any scripts that install. They all follow the copy-paste rule and run automatically, without any problems. However, ProxMenux installs, and in this sense, it's different from the rest of the scripts. The fact that the installer is lighter doesn't change much in this case. I've tried to imagine ProxMenux (maintaining all its functionality) without installation, to make it more standard, but I haven't been able to.
Thanks