-
-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to update Filebrowser #929
Comments
Add an "upgrade" option and change "uninstall" to "remove". The upgrade option, just allows the script to continue installing the latest version. This is in response to: community-scripts#929
Thanks for your effort, but you made the pull request against you own repo. On the other hand i had a look on your code and it dose not do anything updatewise. It just dose a echo command. @MickLesk we should probably rebuild it entierly to fit the new system instead of patching that? |
Not so easy, its not an LXC Script. You can execute this in all LXCs |
Can you test it? bash -c "$(wget -qLO - https://github.com/MickLesk/Proxmox_DEV/raw/main/misc/filebrowser.sh)" |
Just tried, the script went through successful, but the running version is still the old one. Do i need to restart the service maybe? Edit: |
Ok, i Update the Script on monday and create an pr |
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
Filebrowser
π What was the exact command used to execute the script?
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/filebrowser.sh)"
π Provide a clear and concise description of the issue.
Hi,
first of all thanks for all the effort, these scripts are saving a lot of time for all of us.
Is it possible to update the script for Filebrowser so that it has the ability to update the app, like with most other scripts?
βοΈ What settings are you using?
π₯οΈ Which Linux distribution are you using?
Debian 12
π Steps to reproduce the issue.
...
β Paste the full error output (if available).
...
πΌοΈ Additional context (optional).
No response
The text was updated successfully, but these errors were encountered: