liaralabs

I believe other plugins like shellcheck let you apply individual project settings even within a workspace. The `shfmt.flag` setting is greyed out within my project folder; however the `shellcheck` options...

On my installation of trackarr and with someone I just helped support with this, I would say that the base URLs are required.

 Need to update Sonarr to uppercase, but also fix the user variable.

Still getting two of the same errors as before:  nginx is trying to restart the service before it even exists yet radarr user variable is not correctly defined

Care needs to be taken with this PR as the rebase has reintroduced the old Sonarr config dir path (that is `sonarr` instead of `Sonarr`)

> What about prowlarr, readarr, and lidarr? Prowlarr and Lidarr have already implemented this method of setting variables. Readarr is still a PR, so the changes would be targeted there....

The panel needs to be able to read `/root/swizzin` if we move the install locks here. Not sure I feel good about giving the panel read access to `/root` :confused:...

Yeah, the locks are not sensitive data in the slightest, so that would work, as long as we secure the subdirs with appropriate permissions. That said, if we are encrypting...

Is your seedbox hosted on a swizzin installation as well?

You've said the system/status gives you that error message, but what about the log entry from any of the applications when you try testing the connection to the rpc endpoint?