The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
It just could end up creating a permissions mess, so it's better to just avoid entirely.
For this example we're going to make use of a share called data.
The data folder has sub-folders for torrents and usenet and each of these have sub-folders for tv, movie and music downloads to keep things neat. The media folder has nicely named TV, Movies and Music sub-folders, this is your library and what you’d pass to Plex, Emby or JellyFin.
The data folder has sub-folders for torrents and usenet and each of these have sub-folders for tv, movie, books and music downloads to keep things neat. The media folder has nicely named TV, Movies, Books and Music sub-folders, this is your library and what you’d pass to Plex, Emby or JellyFin.
In this examples I'm using lower case on all folder on purpose, being Linux is case sensitive.
+data
├── torrents
-│ ├── movies
-│ ├── music
-│ └── tv
+│ ├── books
+│ ├── movies
+│ ├── music
+│ └── tv
├── usenet
-│ ├── movies
-│ ├── music
-│ └── tv
+│ ├── books
+│ ├── movies
+│ ├── music
+│ └── tv
└── media
- ├── movies
- ├── music
- └── tv
+ ├── books
+ ├── movies
+ ├── music
+ └── tv
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv and /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
The default path setup suggested by some docker developers that encourages people to use mounts like /movies, /tv, /books or /downloads is very suboptimal and it makes them look like two or three file systems, even if they aren’t (Because of how Docker’s volumes work). It is the easiest way to get started. While easy to use, it has a major drawback. Mainly losing the ability to hardlink or instant move, resulting in a slower and more I/O intensive copy + delete is used.
qBittorrent, Deluge, ruTorrent
The reason why we use /data/torrents for the torrent client is because it only needs access to the torrent files. In the torrent software settings, you’ll need to reconfigure paths and you can sort into sub-folders like /data/torrents/{tv|movies|music}.
data
└── torrents
- ├── movies
- ├── music
- └── tv
+ ├── books
+ ├── movies
+ ├── music
+ └── tv
NZBGet or SABnzbd
The reason why we use /data/usenet for the usenet client is because it only needs access to the usenet files. In the usenet software settings, you’ll need to reconfigure paths and you can sort into sub-folders like /data/usenet/{tv|movies|music}.
data
└── usenet
- ├── movies
- ├── music
- └── tv
+ ├── books
+ ├── movies
+ ├── music
+ └── tv
Sonarr, Radarr and Lidarr
-Sonarr, Radarr and Lidarr gets access to everything because the download folder(s) and media folder will look like and be one file system. Hard links will work and moves will be atomic, instead of copy + delete.
+Sonarr, Radarr, Readarr and Lidarr
+Sonarr, Radarr, Readarr and Lidarr gets access to everything using /data because the download folder(s) and media folder will look like and be one file system. Hardlinks will work and moves will be atomic, instead of copy + delete.
data
├── torrents
-│ ├── movies
-│ ├── music
-│ └── tv
+│ ├── books
+│ ├── movies
+│ ├── music
+│ └── tv
├── usenet
-│ ├── movies
-│ ├── music
-│ └── tv
+│ ├── books
+│ ├── movies
+│ ├── music
+│ └── tv
└── media
- ├── movies
- ├── music
- └── tv
+ ├── books
+ ├── movies
+ ├── music
+ └── tv
Plex, Emby, JellyFin and Bazarr
-Plex, Emby, JellyFin and Bazarr only needs access to your media library, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.
+Plex, Emby, JellyFin and Bazarr only needs access to your media library using /data/media, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.
data
└── media
- ├── movies
- ├── music
- └── tv
+ ├── movies
+ ├── music
+ ├── books
+ └── tv
Don't forget to look at the Examples how to setup the paths inside the applications.
diff --git a/Hardlinks/How-to-setup-for/Dockstarter/index.html b/Hardlinks/How-to-setup-for/Dockstarter/index.html index dbe56c76c..9a0a5fad5 100644 --- a/Hardlinks/How-to-setup-for/Dockstarter/index.html +++ b/Hardlinks/How-to-setup-for/Dockstarter/index.html @@ -1066,14 +1066,17 @@ In this example the mounted drive will be mounted to/mnt/ with the
│ ├── torrents
│ │ ├── movies
│ │ ├── music
+| | ├── books
│ │ └── tv
│ └── usenet
│ ├── movies
│ ├── music
+| ├── books
│ └── tv
└── medialibrary
├── movies
├── music
+ ├── books
└── tv
/mnt/ with the
Last update:
- August 15, 2022 16:42:07
+ January 14, 2023 19:30:59