Deployed 37c300b with MkDocs version: 1.5.2

Hardlinks/How-to-setup-for/Docker/index.html

@@ -2617,7 +2617,7 @@ <h2 id="folder-structure">Folder Structure<a class="headerlink" href="#folder-st
 <p>For this example we're going to make use of a share called <code>data</code>.</p>
 <p>The <code>data</code> folder has sub-folders for <code>torrents</code> and <code>usenet</code> and each of these have sub-folders for <code>tv</code>, <code>movie</code>, <code>books</code> and <code>music</code> downloads to keep things neat. The <code>media</code> folder has nicely named <code>TV</code>, <code>Movies</code>, <code>Books</code> and <code>Music</code> sub-folders, this is your library and what you’d pass to Plex, Emby or JellyFin.</p>
 <p><em>In this examples I'm using lower case on all folder on purpose, being Linux is case sensitive.</em></p>
-<!-- BEGIN INCLUDE docker-tree-full.md -->
+<!-- BEGIN INCLUDE ./docker-tree-full.md -->
 <div class="highlight"><pre><span></span><code>data
 ├── torrents
 │   ├── books
@@ -2655,7 +2655,7 @@ <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a c
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link"></a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
 <p>The reason why we use <code>/data/torrents</code> 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 <code>/data/torrents/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-torrents.md -->
+<!-- BEGIN INCLUDE ./docker-tree-torrents.md -->
 <div class="highlight"><pre><span></span><code>data
 └── torrents
      ├── books
@@ -2670,7 +2670,7 @@ <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-cli
 <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-clients" title="Permanent link"></a></h4>
 <p>NZBGet or SABnzbd</p>
 <p>The reason why we use <code>/data/usenet</code> 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 <code>/data/usenet/complete/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-usenet.md -->
+<!-- BEGIN INCLUDE ./docker-tree-usenet.md -->
 <div class="highlight"><pre><span></span><code>data
 └── usenet
     ├── incomplete
@@ -2687,7 +2687,7 @@ <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-client
 <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-apps" title="Permanent link"></a></h4>
 <p>Sonarr, Radarr, Readarr and Lidarr</p>
 <p>Sonarr, Radarr, Readarr and Lidarr gets access to everything using <code>/data</code> 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.</p>
-<!-- BEGIN INCLUDE docker-tree-full.md -->
+<!-- BEGIN INCLUDE ./docker-tree-full.md -->
 <div class="highlight"><pre><span></span><code>data
 ├── torrents
 │   ├── books
@@ -2714,7 +2714,7 @@ <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-app
 <h4 id="media-server">Media Server<a class="headerlink" href="#media-server" title="Permanent link"></a></h4>
 <p>Plex, Emby, JellyFin and Bazarr</p>
 <p>Plex, Emby, JellyFin and Bazarr only needs access to your media library using <code>/data/media</code>, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.</p>
-<!-- BEGIN INCLUDE docker-tree-media.md -->
+<!-- BEGIN INCLUDE ./docker-tree-media.md -->
 <div class="highlight"><pre><span></span><code>data
 └── media
      ├── movies

Hardlinks/How-to-setup-for/Native/index.html

@@ -2553,7 +2553,7 @@ <h2 id="folder-structure">Folder Structure<a class="headerlink" href="#folder-st
 <p>For this example we're going to make use of a share called <code>data</code>.</p>
 <p>The <code>data</code> folder has sub-folders for <code>torrents</code> and <code>usenet</code> and each of these have sub-folders for <code>tv</code>, <code>movie</code>, <code>books</code> and <code>music</code> downloads to keep things neat. The <code>media</code> folder has nicely named <code>TV</code>, <code>Movies</code>, <code>Books</code> and <code>Music</code> sub-folders, this is your library and what you’d pass to Plex, Emby or JellyFin.</p>
 <p><em>In this examples I'm using lower case on all folder on purpose, being Linux is case sensitive.</em></p>
-<!-- BEGIN INCLUDE docker-tree-full.md -->
+<!-- BEGIN INCLUDE ./docker-tree-full.md -->
 <div class="highlight"><pre><span></span><code>data
 ├── torrents
 │   ├── books
@@ -2583,7 +2583,7 @@ <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a c
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link"></a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
 <p>The reason why we use <code>/data/torrents</code> 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 <code>/data/torrents/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-torrents.md -->
+<!-- BEGIN INCLUDE ./docker-tree-torrents.md -->
 <div class="highlight"><pre><span></span><code>data
 └── torrents
      ├── books
@@ -2596,7 +2596,7 @@ <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-cli
 <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-clients" title="Permanent link"></a></h4>
 <p>NZBGet or SABnzbd</p>
 <p>The reason why we use <code>/data/usenet</code> 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 <code>/data/usenet/complete/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-usenet.md -->
+<!-- BEGIN INCLUDE ./docker-tree-usenet.md -->
 <div class="highlight"><pre><span></span><code>data
 └── usenet
     ├── incomplete
@@ -2611,7 +2611,7 @@ <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-client
 <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-apps" title="Permanent link"></a></h4>
 <p>Sonarr, Radarr, Readarr and Lidarr</p>
 <p>Sonarr, Radarr, Readarr and Lidarr gets access to everything using <code>/data</code> 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.</p>
-<!-- BEGIN INCLUDE docker-tree-full.md -->
+<!-- BEGIN INCLUDE ./docker-tree-full.md -->
 <div class="highlight"><pre><span></span><code>data
 ├── torrents
 │   ├── books
@@ -2636,7 +2636,7 @@ <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-app
 <h4 id="media-server">Media Server<a class="headerlink" href="#media-server" title="Permanent link"></a></h4>
 <p>Plex, Emby, JellyFin and Bazarr</p>
 <p>Plex, Emby, JellyFin and Bazarr only needs access to your media library using <code>/data/media</code>, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.</p>
-<!-- BEGIN INCLUDE docker-tree-media.md -->
+<!-- BEGIN INCLUDE ./docker-tree-media.md -->
 <div class="highlight"><pre><span></span><code>data
 └── media
      ├── movies

Hardlinks/How-to-setup-for/Synology/index.html

@@ -3062,7 +3062,7 @@ <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a c
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link"></a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
 <p>The reason why we use <code>/data/torrents</code> 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 <code>/data/torrents/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-torrents.md -->
+<!-- BEGIN INCLUDE ./docker-tree-torrents.md -->
 <div class="highlight"><pre><span></span><code>data
 └── torrents
      ├── books
@@ -3077,7 +3077,7 @@ <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-cli
 <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-clients" title="Permanent link"></a></h4>
 <p>NZBGet or SABnzbd</p>
 <p>The reason why we use <code>/data/usenet</code> 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 <code>/data/usenet/complete/{tv|movies|music}</code>.</p>
-<!-- BEGIN INCLUDE docker-tree-usenet.md -->
+<!-- BEGIN INCLUDE ./docker-tree-usenet.md -->
 <div class="highlight"><pre><span></span><code>data
 └── usenet
     ├── incomplete
@@ -3094,7 +3094,7 @@ <h4 id="usenet-clients">Usenet clients<a class="headerlink" href="#usenet-client
 <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-apps" title="Permanent link"></a></h4>
 <p>Sonarr, Radarr, Readarr and Lidarr</p>
 <p>Sonarr, Radarr, Readarr and Lidarr gets access to everything using <code>/data</code> 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.</p>
-<!-- BEGIN INCLUDE docker-tree-full.md -->
+<!-- BEGIN INCLUDE ./docker-tree-full.md -->
 <div class="highlight"><pre><span></span><code>data
 ├── torrents
 │   ├── books
@@ -3121,7 +3121,7 @@ <h4 id="the-starr-apps">The Starr Apps<a class="headerlink" href="#the-starr-app
 <h4 id="media-server">Media Server<a class="headerlink" href="#media-server" title="Permanent link"></a></h4>
 <p>Plex, Emby, JellyFin and Bazarr</p>
 <p>Plex, Emby, JellyFin and Bazarr only needs access to your media library using <code>/data/media</code>, which can have any number of sub folders like Movies, Kids Movies, TV, Documentary TV and/or Music as sub folders.</p>
-<!-- BEGIN INCLUDE docker-tree-media.md -->
+<!-- BEGIN INCLUDE ./docker-tree-media.md -->
 <div class="highlight"><pre><span></span><code>data
 └── media
      ├── movies

requirements.txt

@@ -5,5 +5,5 @@ mkdocs-macros-plugin==1.0.2
 mkdocs-material==9.1.21
 mkdocs-minify-plugin==0.7.1
 mkdocs-redirects==1.2.1
-mkdocs-include-markdown-plugin==4.0.4
+mkdocs-include-markdown-plugin==6.0.0
 mkdocs-markdownextradata-plugin==0.2.5