Prowlarr update

[memilanuk]

Any idea when we're going to see a new version of the prowlarr script? Got a notice this morning from NZBfinder that the current version is no longer supported and will not be allowed access.

[tremor021]

what do you mean? we install the latest release from their github

[memilanuk]

Well... apparently the Proxmox Scripts LXC updater isn't catching it - or I'm missing the point of what that script is supposed to do?

I did the update 'manually' in the Prowlarr dashboard / control panel under 'settings', and it seems to have done the job.

[tremor021]

Update function deletes the /opt/Prowlarr directory and deploys a new version binary from their github. Not sure what issues you have, but without logs or something we cant debug this.

rm -rf /opt/Prowlarr
fetch_and_deploy_gh_release "prowlarr" "Prowlarr/Prowlarr" "prebuild" "latest" "/opt/Prowlarr" "Prowlarr.master*linux-core-x64.tar.gz"
chmod 775 /opt/Prowlarr

[memilanuk]

Not sure what logs or something you want.

I've been running this community script for on-demand updates of containers, and also have the cron version supposedly running to do the same on a regular (weekly) basis. The LXC Updater ran through all the containers - including Prowlarr - showing zero updates available, immediately before I kicked off the update from 1.37.x to 2.05.x within Prowlarr itself.

I'm getting the impression that the LXC updater scripts only update the container OS, not the actual app itself... which is kinda misleading.

[oOStroudyOo]

Those scripts only update the OS, not the application.
You'll need to run the Prowlarr script inside the LXC to update Prowlarr.
or you can simply type update on the LXC and it'll update your apps.

On run, you'll see a window that looks like this:

[tremor021]

This script has been created to simplify and speed up the process of updating all LXC containers across various Linux distributions, such as Ubuntu, Debian, Devuan, Alpine Linux, CentOS-Rocky-Alma, Fedora, and ArchLinux. It's designed to automatically skip templates and specific containers during the update, enhancing its convenience and usability.

The description clearly states its for updating the container, not the installed apps. I'm feeling like writing these script descriptions is becoming pointless because noone makes even the slightest effort to read them. Yes, the script updates the container OS, not the application.

Every container has the update command that executes application update function specifically (if available).

[memilanuk]

Well, first off, thank you for clarifying that; it was clearly a misunderstanding on my part not a problem with any of the scripts.

That said... I don't think it's a matter of not making "even the slightest effort to read" the description, because I definitely did, several times, before I ever posted. My take away from reading that description - and having used the update script more than a few times - was that it would (and does) allow the user to skip updating specific containers. I've used that functionality in the past. The other bit, about 'templates'... was less clear, at least to me. When we're talking about install 'scripts' for various 'apps', it wasn't inherently obvious to me what 'templates' referred to. Thus I made some assumptions, and well... we know where that ended up ;)

Every container has the update command that executes application update function specifically (if available).

Okay, that is excellent information that I was not aware of (obviously). Literally just now found where it shows up on the pop-up text on the 'updateable' button. A lot of my installs pre-date the newer version of the site, and I don't think that was there back then, so I probably didn't look at the pop-up text on that as closely as I should have. My bad.

If I were going to offer one small constructive suggestion, maybe it would be appropriate to include in the updater script description something specific about using the update command within the container to update the script/apt itself. I'm guessing I'm maybe not the only one who doesn't necessarily connect template=app/script in their mind otherwise. Or maybe I am ;)

Either way, thank you for the help on this. Now I know ;)

[tremor021]

update bash command is just executing the same bash call you used to deploy the container. Our backend detects if the script is executed inside existing LXC or on PVE host. If it detects LXC then it executes the update function, if it detects PVE host it runs normal installation.

I don't really blame you that much for not knowing this, hardly anyone reads our documentation. We specifically avoided making a mass application update scripts because it potentialy leads into us breaking loads of LXCs because very often application update leads to breaking change which we cant really know ahead of time. This could wreak havoc on peoples homelabs and we don't want that. We pretty much insist that you update manually, preferably running a backup/snapshot beforehand.