diff --git a/Dockerfile b/Dockerfile index f054fe7..c7441fd 100644 --- a/Dockerfile +++ b/Dockerfile @@ -21,10 +21,7 @@ RUN \ autoconf \ automake \ build-base \ - cargo \ libffi-dev \ - libxml2-dev \ - libxslt-dev \ openssl-dev \ python3-dev && \ apk add -U --update --no-cache \ diff --git a/Dockerfile.aarch64 b/Dockerfile.aarch64 index ab759de..5d96d94 100644 --- a/Dockerfile.aarch64 +++ b/Dockerfile.aarch64 @@ -21,10 +21,7 @@ RUN \ autoconf \ automake \ build-base \ - cargo \ libffi-dev \ - libxml2-dev \ - libxslt-dev \ openssl-dev \ python3-dev && \ apk add -U --update --no-cache \ diff --git a/README.md b/README.md index 3b06447..a69652f 100644 --- a/README.md +++ b/README.md @@ -73,17 +73,13 @@ Initial setup is done via `http://:` ie, http: See the [SABnzbd wiki](https://sabnzbd.org/wiki/) for more information. -### nzb-notify - -nzb-notify is included with this image as a convenience script. To use it set the Scripts folder in the Folder settings to /app/nzbnotify and then configure it under Notifications. See [nzb-notify](https://github.com/caronc/nzb-notify/) for more information. - ### Download folders -In Sabnzbd gui settings, under `Folders`, make sure to set the `Completed Download Folder` as `/downloads` and the `Temporary Download Folder` as `/incomplete-downloads` +In SABnzbd GUI settings, under `Folders`, make sure to set the `Completed Download Folder` as `/downloads` and the `Temporary Download Folder` as `/incomplete-downloads` We have set `/incomplete-downloads` and `/downloads` as ***optional paths***, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content. -Use the optional paths if you dont understand, or dont want hardlinks/atomic moves. +Use the optional paths if you don't understand, or don't want hardlinks/atomic moves. The folks over at servarr.com wrote a good [write-up](https://wiki.servarr.com/docker-guide#consistent-and-well-planned-paths) on how to get started with this. diff --git a/readme-vars.yml b/readme-vars.yml index ccff985..7a49019 100644 --- a/readme-vars.yml +++ b/readme-vars.yml @@ -37,17 +37,13 @@ app_setup_block: | See the [SABnzbd wiki](https://sabnzbd.org/wiki/) for more information. - ### nzb-notify - - nzb-notify is included with this image as a convenience script. To use it set the Scripts folder in the Folder settings to /app/nzbnotify and then configure it under Notifications. See [nzb-notify](https://github.com/caronc/nzb-notify/) for more information. - ### Download folders - In Sabnzbd gui settings, under `Folders`, make sure to set the `Completed Download Folder` as `/downloads` and the `Temporary Download Folder` as `/incomplete-downloads` + In SABnzbd GUI settings, under `Folders`, make sure to set the `Completed Download Folder` as `/downloads` and the `Temporary Download Folder` as `/incomplete-downloads` We have set `/incomplete-downloads` and `/downloads` as ***optional paths***, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content. - Use the optional paths if you dont understand, or dont want hardlinks/atomic moves. + Use the optional paths if you don't understand, or don't want hardlinks/atomic moves. The folks over at servarr.com wrote a good [write-up](https://wiki.servarr.com/docker-guide#consistent-and-well-planned-paths) on how to get started with this.