haeaeae/docker-sabnzbd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove ambiguity around download paths

Browse Source
This commit is contained in:
thespad
2024-07-14 18:04:34 +01:00
parent 86e34b0fd1
commit c26ecb864b
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme-vars.yml
+3 -5
View File
@@ -35,17 +35,15 @@ readonly_supported: true
# application setup block
app_setup_block_enabled: true
app_setup_block: |
Initial setup is done via `http://<docker host ip>:<mapped http port>` ie, http://192.168.1.100:8080.
Initial setup is done via `http://<your-ip>:8080`.
See the [SABnzbd wiki](https://sabnzbd.org/wiki/) 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`
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 for atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.
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 don't understand, or don't want hardlinks/atomic moves.
Use the optional paths if you don't understand, or don't want atomic moves. Whichever paths you choose to use, make sure to set the `Completed Download Folder` as `/downloads` and the `Temporary Download Folder` as `/incomplete-downloads` in the SABnzbd gui settings, under `Folders`.
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.