SVI/ProxmoxVE-Local
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE-Local.git synced 2026-03-31 06:23:54 -04:00
Code Issues 56 Packages Projects Releases 7 Wiki Activity

Preset Configurations per PVE Server #30

New Issue
Open
opened 2025-11-20 04:12:03 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:12:03 -05:00
Owner
Copy Link

Originally created by @gdeeble on GitHub (Oct 9, 2025).

🌟 Briefly describe the feature

Scripts contain the ability to have some defaults, moving this into the UI would help manage it on a server by server basis

📝 Detailed description

Today the install scripts can read from a file with predefined values to speed up the process. To make this process manageable, exposing these values to the UI on a server by server basis so you can update them there could help streamline the installation.

When you click install, the page could ask you what the container name should be and potentially the password and if you want to use the defaults for the server selected, then pass them to the script thus making it really a point and click solution.

💡 Why is this useful?

By adding the ability to create defaults in UI, you can easily manage them and have the scripts auto run by passing some variables in and the configuration items. This will reduce the time it might take create a container and help keep the environment consistent.

Originally created by @gdeeble on GitHub (Oct 9, 2025). ### 🌟 Briefly describe the feature Scripts contain the ability to have some defaults, moving this into the UI would help manage it on a server by server basis ### 📝 Detailed description Today the install scripts can read from a file with predefined values to speed up the process. To make this process manageable, exposing these values to the UI on a server by server basis so you can update them there could help streamline the installation. When you click install, the page could ask you what the container name should be and potentially the password and if you want to use the defaults for the server selected, then pass them to the script thus making it really a point and click solution. ### 💡 Why is this useful? By adding the ability to create defaults in UI, you can easily manage them and have the scripts auto run by passing some variables in and the configuration items. This will reduce the time it might take create a container and help keep the environment consistent.
saavagebueno added the enhancement label 2025-11-20 04:12:03 -05:00
saavagebueno commented 2025-11-20 04:12:03 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 9, 2025):

Uh, i like that idea.
We have to wait for some changes in the main repo backendstuff, then i can implement that!

@michelroegl-brunner commented on GitHub (Oct 9, 2025): Uh, i like that idea. We have to wait for some changes in the main repo backendstuff, then i can implement that!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
feature
in progress
pull-request
Mirrored from GitHub Pull Request
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE-Local#30
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?