starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Integrate ProxMenux administration script #1052

New Issue
Closed
opened 2026-02-04 22:48:43 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 22:48:43 +03:00
Owner
Copy Link

Originally created by @migueldeblas on GitHub (Jun 2, 2025).

🌟 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.

Originally created by @migueldeblas on GitHub (Jun 2, 2025). ### 🌟 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.
OVERLORD added the enhancement label 2026-02-04 22:48:43 +03:00
OVERLORD commented 2026-02-04 22:48:52 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 2, 2025):

https://github.com/community-scripts/ProxmoxVE/discussions/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?

@MickLesk commented on GitHub (Jun 2, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/1452 but i dont know, how we can integrate this. its "useless" to bash call and script in our repo to use this. :smile: 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?
OVERLORD commented 2026-02-04 22:48:57 +03:00
Author
Owner
Copy Link

@MacRimi commented on GitHub (Jun 2, 2025):

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.

  1. 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?

@MacRimi commented on GitHub (Jun 2, 2025): 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](https://github.com/community-scripts/ProxmoxVE/discussions/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?
OVERLORD commented 2026-02-04 22:48:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 2, 2025):

  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

@MickLesk commented on GitHub (Jun 2, 2025): 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
OVERLORD commented 2026-02-04 22:49:02 +03:00
Author
Owner
Copy Link

@MacRimi commented on GitHub (Jun 2, 2025):

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!

@MacRimi commented on GitHub (Jun 2, 2025): 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!
OVERLORD commented 2026-02-04 22:49:06 +03:00
Author
Owner
Copy Link

@migueldeblas commented on GitHub (Jun 2, 2025):

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.

@migueldeblas commented on GitHub (Jun 2, 2025): 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.
OVERLORD commented 2026-02-04 22:49:15 +03:00
Author
Owner
Copy Link

@MacRimi commented on GitHub (Jun 2, 2025):

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!

@MacRimi commented on GitHub (Jun 2, 2025): 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!
OVERLORD commented 2026-02-04 22:49:20 +03:00
Author
Owner
Copy Link

@migueldeblas commented on GitHub (Jun 2, 2025):

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

@migueldeblas commented on GitHub (Jun 2, 2025): 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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1052
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?