Closed pvillano closed 1 year ago
We usually don't allow updating inside the container unless it is absolutely necessary (ie. nextcloud, plex beta, etc.). Jackett for a long time did not allow updates inside the container. But then the upstream dev requested and insisted we add it because it made it easier for their support team. So we did. The readme on the master branch is accurate. It seems we neglected to update the readme on the develop branch when we added that functionality in.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Desired Behavior
Consistency between
readme.md
, itself, anddocker-jackett/root/etc/services.d/jackett/run
.Probably removal of
AUTO_UPDATE
environment variable fromREADME.md
andrun
;--NoUpdates
always onCurrent Behavior
Inconsistent information regarding autoupdates on master branch
-e AUTO_UPDATE=true
| Allow Jackett to update inside of the container (currently recommended by Jackett and enabled by default)In the development branch,
docker-jackett/root/etc/services.d/jackett/run
still reads the environment variableAlternatives Considered
going outside for a bit