Merge pull request #1085 from TRaSH-/dockerwording

docker wording updates
pull/1096/head
TRaSH 1 year ago committed by GitHub
commit 7714d4ce59
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -15,14 +15,17 @@ storage
│ ├── torrents
│ │ ├── movies
│ │ ├── music
| | ├── books
│ │ └── tv
│ └── usenet
│ ├── movies
│ ├── music
| ├── books
│ └── tv
└── medialibrary
├── movies
├── music
├── books
└── tv
```

@ -148,21 +148,7 @@ These subfolders you need to create your self.
*I'm using lower case on all folder on purpose, being Linux is case sensitive.*
```none
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-full.md" !}
{! include-markdown "../../../includes/hardlinks/bad-path-suggestion.md" !}
<!-- --8<-- "includes/hardlinks/bad-path-suggestion.md" -->

@ -45,21 +45,7 @@ The `data` folder has sub-folders for `torrents` and `usenet` and each of these
These subfolders you need to create your self, you can use krusader or winscp to create them or any other way you prefer.
```none
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-full.md" !}
*I'm using lower case on all folder on purpose, being Linux is case sensitive.*
@ -98,13 +84,7 @@ 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, youll need to reconfigure paths and you can sort into sub-folders like `/data/torrents/{tv|movies|music}`.
```none
data
└── torrents
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-torrents.md" !}
------
@ -122,13 +102,7 @@ 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, youll need to reconfigure paths and you can sort into sub-folders like `/data/usenet/{tv|movies|music}`.
```none
data
└── usenet
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-usenet.md" !}
------
@ -146,21 +120,7 @@ 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.
```none
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-full.md" !}
------
@ -178,13 +138,7 @@ 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.
```none
data
└── media
├── movies
├── music
└── tv
```
{! include-markdown "../../../includes/hardlinks/docker-tree-media.md" !}
------

@ -1,3 +1,3 @@
!!! warning ""
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 arent (*Because of how Dockers 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 arent (*Because of how Dockers 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.

@ -6,13 +6,7 @@ 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, youll need to reconfigure paths and you can sort into sub-folders like `/data/torrents/{tv|movies|music}`.
```none
data
└── torrents
├── movies
├── music
└── tv
```
{! include-markdown "docker-tree-torrents.md" !}
#### Usenet clients
@ -20,49 +14,23 @@ 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, youll need to reconfigure paths and you can sort into sub-folders like `/data/usenet/{tv|movies|music}`.
```none
data
└── usenet
├── movies
├── music
└── tv
```
{! include-markdown "docker-tree-usenet.md" !}
#### The Starr Apps
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.
```none
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv
```
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.
{! include-markdown "docker-tree-full.md" !}
#### Media Server
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.
```none
data
└── media
├── movies
├── music
└── tv
```
{! include-markdown "docker-tree-media.md" !}
------

@ -0,0 +1,18 @@
```none
data
├── torrents
│ ├── books
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── books
│ ├── movies
│ ├── music
│ └── tv
└── media
├── books
├── movies
├── music
└── tv
```

@ -0,0 +1,8 @@
```none
data
└── media
├── movies
├── music
├── books
└── tv
```

@ -0,0 +1,8 @@
```none
data
└── torrents
├── books
├── movies
├── music
└── tv
```

@ -0,0 +1,8 @@
```none
data
└── usenet
├── books
├── movies
├── music
└── tv
```

@ -12,22 +12,8 @@
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 youd 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 youd pass to Plex, Emby or JellyFin.
*In this examples I'm using lower case on all folder on purpose, being Linux is case sensitive.*
```none
data
├── torrents
│ ├── movies
│ ├── music
│ └── tv
├── usenet
│ ├── movies
│ ├── music
│ └── tv
└── media
├── movies
├── music
└── tv
```
{! include-markdown "docker-tree-full.md" !}

Loading…
Cancel
Save