Add ability to repoint the repo for scripts #32

Closed
opened 2025-11-20 04:12:04 -05:00 by saavagebueno · 3 comments
Owner

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

🌟 Briefly describe the feature

Add ability to repoint the repo for scripts so they can be hosted anywhere

📝 Detailed description

Add the ability to repoint the repo using the UI so that a user can clone the current repo and use their own clone. This allows users to develop scripts that can be merged at a later time with the main community scripts repo, or allow them to keep copies of their scripts that they may have made for personalization and still be able to install/update them on their own without necessitating the need for a manual installation.

This might require some alterations to all scripts(this, as well as the install/update scripts), including making the domain a variable in the installation scripts, but would provide flexibility for everyone

💡 Why is this useful?

By adding this, a user can utilize the main repo or provide a custom repo where they can develop/update/maintain scripts that may be publicly usable or privately usable. It can allow developers to build a process and test it without the need to use SSH and/or have direct access to the host since it goes through a tunnel. They could build the process and put it in the repo, then execute it from the UI.

Originally created by @gdeeble on GitHub (Oct 9, 2025). ### 🌟 Briefly describe the feature Add ability to repoint the repo for scripts so they can be hosted anywhere ### 📝 Detailed description Add the ability to repoint the repo using the UI so that a user can clone the current repo and use their own clone. This allows users to develop scripts that can be merged at a later time with the main community scripts repo, or allow them to keep copies of their scripts that they may have made for personalization and still be able to install/update them on their own without necessitating the need for a manual installation. This might require some alterations to all scripts(this, as well as the install/update scripts), including making the domain a variable in the installation scripts, but would provide flexibility for everyone ### 💡 Why is this useful? By adding this, a user can utilize the main repo or provide a custom repo where they can develop/update/maintain scripts that may be publicly usable or privately usable. It can allow developers to build a process and test it without the need to use SSH and/or have direct access to the host since it goes through a tunnel. They could build the process and put it in the repo, then execute it from the UI.
saavagebueno added the enhancement label 2025-11-20 04:12:04 -05:00
Author
Owner

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

I need to think that through. It is so tailored to our main repo that i dont know if this will be possible to work with any repo, as we use the same scripts and backend stuff. But i will keep it in mind.

@michelroegl-brunner commented on GitHub (Oct 9, 2025): I need to think that through. It is so tailored to our main repo that i dont know if this will be possible to work with any repo, as we use the same scripts and backend stuff. But i will keep it in mind.
Author
Owner

@michelroegl-brunner commented on GitHub (Nov 13, 2025):

Done in 0.4.11 :)

@michelroegl-brunner commented on GitHub (Nov 13, 2025): Done in 0.4.11 :)
Author
Owner

@gdeeble commented on GitHub (Nov 13, 2025):

Awesome. Thank you!

@gdeeble commented on GitHub (Nov 13, 2025): Awesome. Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE-Local#32