Deployed 38d9d911 with MkDocs version: 1.3.1

Downloaders/Deluge/Deluge-Basic-Setup/index.html

@@ -2130,7 +2130,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

Downloaders/NZBGet/Basic-Setup/index.html

@@ -2310,7 +2310,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

Downloaders/SABnzbd/Basic-Setup/index.html

@@ -2360,7 +2360,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

Downloaders/qBittorrent/Basic-Setup/index.html

@@ -2468,7 +2468,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

Downloaders/qBittorrent/Tips/How-to-run-the-unRaid-mover-for-qBittorrent/index.html

@@ -2306,7 +2306,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

Downloaders/ruTorrent/ruTorrent-Basic-Setup/index.html

@@ -2130,7 +2130,7 @@
 <p>More info <a href="/Hardlinks/Hardlinks-and-Instant-Moves/" rel="noopener noreferrer" target="_blank">HERE</a></p>
 </div>
 <div class="admonition attention">
-<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal because it makes them look like two or three file systems, even if they aren’t. 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.</p>
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 <p>But you're able to change this, by not using the pre-defined/recommended paths like:</p>
 <ul>
 <li><code>/downloads</code> =&gt; <code>/data/downloads</code>, <code>/data/usenet</code>, <code>/data/torrents</code></li>

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

@@ -2287,10 +2287,6 @@ You may choose to rely on DockSTARTer for various changes to your Docker system
 <p>External paths depends where you mounted your share or your drives.</p>
 <p>For example <code>/&lt;path_to_data&gt;/data</code>, or even <code>/data</code>.</p>
 </div>
-<div class="admonition info">
-<p class="admonition-title">Info</p>
-<p>The paths you use on the inside matter. Because of how Docker’s volumes work, passing in two or three volumes such as the commonly suggested <code>/tv</code>, <code>/movies</code> and <code>/downloads</code> makes them look like two or three file systems, even if they aren’t. This means hard links won’t work and instead of an instant move, a slower and more I/O intensive copy + delete is used.</p>
-</div>
 <h2 id="folder-structure">Folder Structure<a class="headerlink" href="#folder-structure" title="Permanent link">¶</a></h2>
 <div class="admonition attention">
 <p class="admonition-title">Attention</p>
@@ -2316,6 +2312,9 @@ You may choose to rely on DockSTARTer for various changes to your Docker system
    ├── music
    └── tv
 </code></pre></div>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
+</div>
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link">¶</a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
@@ -2471,7 +2470,7 @@ services:
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">December 26, 2021 16:08:48</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>

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

@@ -2682,6 +2682,9 @@ Remember these values for later use.</p>
    ├── music
    └── tv
 </code></pre></div>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
+</div>
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link">¶</a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
@@ -2885,7 +2888,7 @@ If you had previous installed apps, make a backup of their config folders.</p>
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 28, 2022 09:56:37</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>

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

@@ -2337,9 +2337,8 @@
 <p><em>I'm using lower case on all folder on  purpose, being Linux is case sensitive.</em></p>
 <hr />
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
-<div class="admonition info">
-<p class="admonition-title">Info</p>
-<p>The paths you use on the inside matter. Because of how Docker’s volumes work, passing in two or three volumes such as the commonly suggested <code>/tv</code>, <code>/movies</code> and <code>/downloads</code> makes them look like two or three file systems, even if they aren’t. This means hard links won’t work and instead of an instant move, a slower and more I/O intensive copy + delete is used.</p>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 </div>
 <h2 id="setting-up-the-containers">Setting up the containers<a class="headerlink" href="#setting-up-the-containers" title="Permanent link">¶</a></h2>
 <p>After you created all the needed folders it's time to setup the paths in the docker containers.</p>
@@ -2442,7 +2441,7 @@
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">May 22, 2022 20:19:54</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>

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

@@ -2285,10 +2285,6 @@ You may choose to rely on DockSTARTer for various changes to your Docker system
 <p>External paths depends where you mounted your share or your drives.</p>
 <p>For example <code>/&lt;path_to_data&gt;/data</code>, or even <code>/data</code>.</p>
 </div>
-<div class="admonition info">
-<p class="admonition-title">Info</p>
-<p>The paths you use on the inside matter. Because of how Docker’s volumes work, passing in two or three volumes such as the commonly suggested <code>/tv</code>, <code>/movies</code> and <code>/downloads</code> makes them look like two or three file systems, even if they aren’t. This means hard links won’t work and instead of an instant move, a slower and more I/O intensive copy + delete is used.</p>
-</div>
 <h2 id="folder-structure">Folder Structure<a class="headerlink" href="#folder-structure" title="Permanent link">¶</a></h2>
 <div class="admonition attention">
 <p class="admonition-title">Attention</p>
@@ -2314,6 +2310,9 @@ You may choose to rely on DockSTARTer for various changes to your Docker system
    ├── music
    └── tv
 </code></pre></div>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
+</div>
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link">¶</a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
@@ -2469,7 +2468,7 @@ services:
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">December 26, 2021 16:08:48</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>

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

@@ -2680,6 +2680,9 @@ Remember these values for later use.</p>
    ├── music
    └── tv
 </code></pre></div>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
+</div>
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
 <h4 id="torrent-clients">Torrent clients<a class="headerlink" href="#torrent-clients" title="Permanent link">¶</a></h4>
 <p>qBittorrent, Deluge, ruTorrent</p>
@@ -2883,7 +2886,7 @@ If you had previous installed apps, make a backup of their config folders.</p>
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 28, 2022 09:56:37</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>

How-to-setup-for/Unraid/index.html

@@ -2335,9 +2335,8 @@
 <p><em>I'm using lower case on all folder on  purpose, being Linux is case sensitive.</em></p>
 <hr />
 <h3 id="breakdown-of-the-folder-structure">Breakdown of the Folder Structure<a class="headerlink" href="#breakdown-of-the-folder-structure" title="Permanent link">¶</a></h3>
-<div class="admonition info">
-<p class="admonition-title">Info</p>
-<p>The paths you use on the inside matter. Because of how Docker’s volumes work, passing in two or three volumes such as the commonly suggested <code>/tv</code>, <code>/movies</code> and <code>/downloads</code> makes them look like two or three file systems, even if they aren’t. This means hard links won’t work and instead of an instant move, a slower and more I/O intensive copy + delete is used.</p>
+<div class="admonition attention">
+<p>The default path setup suggested by some docker developers that encourages people to use mounts like <code>/movies</code>, <code>/tv</code> and <code>/downloads</code> is very suboptimal  and it makes them look like two or three file systems, even if they aren’t (<em>Because of how Docker’s volumes work</em>). 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.</p>
 </div>
 <h2 id="setting-up-the-containers">Setting up the containers<a class="headerlink" href="#setting-up-the-containers" title="Permanent link">¶</a></h2>
 <p>After you created all the needed folders it's time to setup the paths in the docker containers.</p>
@@ -2440,7 +2439,7 @@
   <small>
     
       Last update:
-      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">May 22, 2022 20:19:54</span>
+      <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">July 31, 2022 09:49:44</span>
       
     
   </small>