Closed thijsjek closed 2 years ago
Thanks for the troubleshooting!
I generally don't like the idea of service users having a home dir, but if that is something that prowlarr
requires I will rework the guide and the service file to account for it.
Having the data and/or config for an app in a different location, however, IS a good idea as you can more easily set it up as a dataset with snapshots that is mounted into a jail. Many people don't do this and from what i've seen, most FreeNAS/TrueNAS guides seem to overlook this benefit. I will also add this to my guide.
This also shows I needed to spend some more time testing prowlarr
before pushing out a package for it. =>.<=
I won't have much free time until later this week to impliment/test changes so a reworked package might not be available until closer to the weekend.
Good that you see the benefit of mounting datasets. No need to rush because above is the work around provided.
Edit... I solved first the ~/.conf dir by having a home directory. And then moving the data dir. Sonarr and radarr both do the same, and just have to move the data dir somewhere else and both issues solved. I shall update above
I have gone ahead and uploaded an updated package.
Two major changes:
It now installs to /usr/local/prowlarr
. I forgot to change this during the change from mono->dotnet. mono
things would go into /usr/local/share/PORTNAME
because its arch agnostic. dotnet is arch specific so it should go into /usr/local/PORTNAME
The data location is now /usr/local/data/prowlarr
. /var
is a bad place because its only for transient data files and /etc
is for system data files. prowlarr
falls under neither and I didn't have a good place to put it lol
@thijsjek ping. did reworked package work for you?
Sorry, got a bit busy. I used a new jail and your new package, and it worked. I had to wait a few days to see if an actual update would work and it did. 10/10.
Glad to hear!
Hi @Thefrank, sorry to reopen this issue, but I just installed Prowlarr following the latest instructions and this issue still persists.
The situation now is the following:
Prowlarr executables are inside /usr/local/prowlarr
and Prowlarr data inside /usr/local/prowlarr/data
, but because the data folder is inside the executables folder the same error appears and prevents updating.
I solved this issue simply specifying a different "prowlarr_data_dir" BEFORE starting Prowlarr for the first time, but I would suggest keeping the same folder structure as Radarr and Sonarr do, so:
/usr/local/share/prowlarr
/usr/local/prowlarr
(Again, this is how Radarr and Sonarr structure their folders inside TrueNAS)Hope this helps! (Awesome job by the way!)
I forgot to update the guide with links to the updated package >.<
I will have to update the guide AGAIN once prowlarr
is added to the official ports system (you can watch the progress here if interested https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259196)
Oh I missed the prowlarrdotnet pkg
, I didn't use the package version written in the guide, but I opened your releases pages and got the latest available .txz prowlarr version (https://github.com/Thefrank/freebsd-port-sooners/releases/download/20210916/prowlarr-0.1.1.875.txz).
But that's ok, as soon as the official port comes out I'll probably do a fresh install, thanks!
I installed as your instruction, but it gave me 2 warnings when trying to update to a newer build trough build-in updater.
Solved by using `sysrc prowlarr_data_dir=/usr/local/prowlarr mkdir /usr/local/prowlarr
cp -R /usr/local/share/prowlarr/data/* /usr/local/prowlarr/
chown -R prowlarr:prowlarr /usr/local/prowlarr`
You can also as pointed out below, mount a dataset and have your data stored on it. Just point /usr/local/prowlarr to /your/mount/point.