Deployed 30b9cb0 with MkDocs version: 1.6.1

This commit is contained in:
2026-08-17 04:20:46 +00:00
parent 0f3e6556aa
commit bc72686e8b
13 changed files with 1364 additions and 1031 deletions
+15
View File
@@ -3303,6 +3303,21 @@ and keeps the service's numbering unchanged. Pick an order that covers the whole
<td>Per-track download threads.</td>
</tr>
<tr>
<td><code>--adaptive-workers</code></td>
<td>off</td>
<td>Scale per-track segment workers dynamically (up to the <code>--workers</code> cap) based on measured CDN throughput and errors.</td>
</tr>
<tr>
<td><code>--download-processes</code></td>
<td><code>1</code></td>
<td>Split large segment batches (24+) across this many download processes to exceed the single-process throughput cap on multi-gigabit connections. Ignored while a speed limit is set: the cap is one shared budget, which extra processes cannot share, so the download stays in a single process.</td>
</tr>
<tr>
<td><code>--continue-downloads</code></td>
<td>off</td>
<td>Keep completed segment files across runs and resume a previously failed download. One-off enable of the <a href="../../reference/configuration/download/#continue_downloads"><code>continue_downloads</code></a> config option.</td>
</tr>
<tr>
<td><code>--downloads</code></td>
<td><code>1</code></td>
<td>Number of tracks downloaded concurrently.</td>
+12
View File
@@ -3670,6 +3670,18 @@ configured proxy providers), or a <code>provider:region</code> form.</p>
<td>Threads used per track for segment downloads. Default depends on the downloader.</td>
</tr>
<tr>
<td><code>--adaptive-workers</code></td>
<td>Opt-in: start with a moderate per-track worker count and ramp it up or back off based on measured CDN throughput and errors, capped at <code>--workers</code>. Off by default (fixed worker count).</td>
</tr>
<tr>
<td><code>--download-processes N</code></td>
<td>Opt-in: split a large segment batch across <code>N</code> download processes, each with its own worker pool. A single process tops out around 1.3 Gb/s (Python interpreter limit); <code>2</code> reaches 2.5GbE line rate on fast CDNs. Only engages for batches of 24+ segments. Ignored while <code>--speed-limit</code> (or serve's <code>global_speed_limit</code>) is set: the cap is one shared budget, which extra processes cannot share, so the download stays in a single process. Default <code>1</code>.</td>
</tr>
<tr>
<td><code>--continue-downloads</code></td>
<td>Opt-in: keep completed segment files when a download fails so the next run resumes instead of restarting from zero. One-off enable of the <a href="../../reference/configuration/download/#continue_downloads"><code>continue_downloads</code></a> config option, which documents what can and cannot resume.</td>
</tr>
<tr>
<td><code>--downloads N</code></td>
<td>Number of tracks downloaded concurrently. Default <code>1</code>.</td>
</tr>
+2
View File
@@ -3124,6 +3124,8 @@ with <a href="../../reference/configuration/download/#language_tags"><code>langu
</span></code></pre></div>
<p>The date separator follows your template style: dots here, spaces if your <code>series</code>
template uses spaces.</p>
<p>In folder names, <code>{season}</code> becomes the air year (<code>Season 2024</code> style grouping), and a
<code>{year?}</code> in the folder template is skipped when it would just repeat that year.</p>
</div>
<div class="tabbed-block">
<p><div class="language-yaml highlight"><pre><span></span><code><span id="__span-34-1"><a id="__codelineno-34-1" name="__codelineno-34-1" href="#__codelineno-34-1"></a><span class="nt">output_template</span><span class="p">:</span>