You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a helper for easier sourcing from development repos聽#1449
but when you're developing it has to go to ProxmoxVED or to your own branch. You may point to your branch properly, but if you didn't modify all instances across the codebase it will point to the original and miss your install/*-install.sh changes. If you're lucky you get an uninformative curl 404 error, and otherwise you end up with the old version. Either way, you get no indication of what was requested, leading to indecipherable and inexplicable errors.
which can be configured by SOURCE_REPO and SOURCE_BRANCH, so that you don't need to modify hundreds of files. Maybe the first one needs the full path, but at the moment you need to modify all files, and this could be mitigated pushing it to a configuration variable that can be set from the cmdline.
You can do a Pull Request in the DEV repo if you like. We had many attempts wich tryed to fix that, but nothing ever worked. So it is not high on our TODO list at this moment.
but when you're developing it has to go to ProxmoxVED or to your own branch. You may point to your branch properly, but if you didn't modify all instances across the codebase it will point to the original and miss your install/*-install.sh changes. If you're lucky you get an uninformative curl 404 error, and otherwise you end up with the old version. Either way, you get no indication of what was requested, leading to indecipherable and inexplicable errors.
@tewalds 馃憤
I'm facing this kind of issue on a regular base ...
For sure, there are workarrounds mentioned above - but I have the strong feeling that a lot of people trying to support this project giving up after a couple of hours without any success.
@ALL: Let's try together and hopefully there is a way to simplyfy.
I spent a literal day trying to understand why nothing worked until I figured this out, and it's still painful testing it every time since the code has to refer to itself, which also makes it unsubmittable. I don't think I'll be contributing again until this is fixed. It's not worth the effort.
Activity
michelroegl-brunner commentedon Feb 11, 2026
You can do a Pull Request in the DEV repo if you like. We had many attempts wich tryed to fix that, but nothing ever worked. So it is not high on our TODO list at this moment.
heinemannj commentedon Feb 13, 2026
@tewalds 馃憤
I'm facing this kind of issue on a regular base ...
For sure, there are workarrounds mentioned above - but I have the strong feeling that a lot of people trying to support this project giving up after a couple of hours without any success.
@ALL: Let's try together and hopefully there is a way to simplyfy.
tewalds commentedon Feb 13, 2026
I spent a literal day trying to understand why nothing worked until I figured this out, and it's still painful testing it every time since the code has to refer to itself, which also makes it unsubmittable. I don't think I'll be contributing again until this is fixed. It's not worth the effort.
feat: add configurable COMMUNITY_SCRIPTS_URL for dev sourcing (#1449)
refactor: clean COMMUNITY_SCRIPTS_URL pattern (#1449)