SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-22 22:03:55 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Caddy not updateable - yet update command runs #994

New Issue
Closed
opened 2025-11-20 04:57:45 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 04:57:45 -05:00
Owner
Copy Link

Originally created by @di5cord20 on GitHub (Apr 28, 2025).

📌 Task summary

Remove update command if it's not updateable

📋 Task details

I blindly ran the update command for Caddy. It worked and updated to the latest version. My Caddy wasn't running and I realized I use xcaddy and had to rebuilt using that command. Later, I noticed that https://community-scripts.github.io/ProxmoxVE/scripts?id=caddy states that Caddy is not updateable. If that is true, why did the update command run?

Not sure if this impacts other scripts that are not updateable???

Originally created by @di5cord20 on GitHub (Apr 28, 2025). ### 📌 Task summary Remove update command if it's not updateable ### 📋 Task details I blindly ran the `update` command for Caddy. It worked and updated to the latest version. My Caddy wasn't running and I realized I use xcaddy and had to rebuilt using that command. Later, I noticed that https://community-scripts.github.io/ProxmoxVE/scripts?id=caddy states that Caddy is not updateable. If that is true, why did the `update` command run? Not sure if this impacts other scripts that are not updateable???
saavagebueno commented 2025-11-20 04:57:46 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 28, 2025):

it updates only the caddy, not xcaddy - xcaddy is an "addon" and should be done manually

msg_info "Updating $APP LXC"
$STD apt-get update
$STD apt-get -y upgrade
msg_ok "Updated $APP LXC"

@MickLesk commented on GitHub (Apr 28, 2025): it updates only the caddy, not xcaddy - xcaddy is an "addon" and should be done manually msg_info "Updating $APP LXC" $STD apt-get update $STD apt-get -y upgrade msg_ok "Updated $APP LXC"
saavagebueno commented 2025-11-20 04:57:46 -05:00
Author
Owner
Copy Link

@di5cord20 commented on GitHub (Apr 28, 2025):

the json for the frontend indicates that this script is not updateable, yet the update worked. I get that the update works for the default and not xcaddy addon. Perhaps a warning to users similar to the one that already exists for xcaddy would be helpful. Just a thought... I now know that I need to update manually. Thanks again for all the great scripts and support.

@di5cord20 commented on GitHub (Apr 28, 2025): the json for the frontend indicates that this script is not updateable, yet the update worked. I get that the update works for the default and not xcaddy addon. Perhaps a warning to users similar to the one that already exists for xcaddy would be helpful. Just a thought... I now know that I need to update manually. Thanks again for all the great scripts and support.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label
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#994
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?