Fix a few broken links

ptarmiganlabs · Apr 15, 2024 · 2413b5c · 2413b5c
1 parent 96c9e73
commit 2413b5c
Show file tree

Hide file tree

Showing 13 changed files with 21 additions and 21 deletions.
diff --git a/content/en/_index.html b/content/en/_index.html
@@ -53,7 +53,7 @@
 Get notified when tasks fail or are stopped, with notifications sent to Slack, Microsoft Teams, email, InfluxDb, New Relic, Signl4 and other destinations.  
 Full support for HTML/Markdown formatting and 40+ template fields.
 
-[Read more...](/docs/concepts/alert-emails/) 
+[Read more...](/docs/concepts/failed-reloads/) 
 {{% /blocks/feature %}}
 
 
@@ -63,7 +63,7 @@
 Butler can save these for you, sorted by date.  
 Finding what caused a reload to fail is now easier than ever!
 
-[Read more...](/docs/concepts/failed-reload-logs/) 
+[Read more...](/docs/concepts/failed-reloads/) 
 {{% /blocks/feature %}}
 
 
@@ -139,7 +139,7 @@
 Extract app metadata for a single or all apps in a Sense cluster.
 Great for backup purposes!
 
-[Read more...](/docs/reference/rest-api/?operationsSorter=alpha) 
+[Read more...](/docs/reference/rest-api-1/?operationsSorter=alpha) 
 {{% /blocks/feature %}}
 
 

diff --git a/content/en/docs/_index.md b/content/en/docs/_index.md
@@ -590,6 +590,6 @@ Key-value stores are a very versatile tool and a great addition to Qlik Sense.
 
 * **API docs** using the OpenAPI/Swagger format.
 
-* A totally **re-engineered REST API** that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs... which was really ugly. The downside is that this is a major breaking change! Please review the [API docs](/docs/reference/rest-api) for details.
+* A totally **re-engineered REST API** that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs... which was really ugly. The downside is that this is a major breaking change! Please review the [API docs](/docs/reference/rest-api-1/) for details.
 
 {{% /pageinfo %}}
diff --git a/content/en/docs/concepts/key-value/_index.md b/content/en/docs/concepts/key-value/_index.md
@@ -25,7 +25,7 @@ Both key and value are strings in Butler's KV store. You must thus make sure to
 
 There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair's last update.
 
-The [API docs](/docs/reference/rest-api) shows what methods are available to work with KV pairs.
+The [API docs](/docs/reference/rest-api-1/) shows what methods are available to work with KV pairs.
 
 ## How can a key-value store be used in Sense apps?
 

diff --git a/content/en/docs/concepts/scheduler/_index.md b/content/en/docs/concepts/scheduler/_index.md
@@ -34,7 +34,7 @@ Features of the Butler scheduler:
 * 5 postition patterns are also supported, the leftmost position then represents minutes.
 * Hundreds of schedules tested and confirmed working as expected.
 * A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.
-* Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using [Butler's API](/docs/reference/rest-api). A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.
+* Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using [Butler's API](/docs/reference/rest-api-1/). A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.
 
 The two supported schedule formats look like this:
 

diff --git a/docs/docs/concepts/index.xml b/docs/docs/concepts/index.xml
@@ -42,7 +42,7 @@
 &lt;/div&gt;
 
 &lt;p&gt;There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair&amp;rsquo;s last update.&lt;/p&gt;
-&lt;p&gt;The &lt;a href=&#34;https://butler.ptarmiganlabs.com/docs/reference/rest-api&#34;&gt;API docs&lt;/a&gt; shows what methods are available to work with KV pairs.&lt;/p&gt;
+&lt;p&gt;The &lt;a href=&#34;https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/&#34;&gt;API docs&lt;/a&gt; shows what methods are available to work with KV pairs.&lt;/p&gt;
 &lt;h2 id=&#34;how-can-a-key-value-store-be-used-in-sense-apps&#34;&gt;How can a key-value store be used in Sense apps?&lt;/h2&gt;
 &lt;p&gt;As mentioned above - A KV store can be useful whenever you need to stash data away for a while and then get it back. I.e. keeping track of the state of something.&lt;/p&gt;
 &lt;p&gt;For example&lt;/p&gt;
@@ -117,7 +117,7 @@ Cron has been the standard scheduler for decades in most Linux systems, it&amp;r
 &lt;li&gt;5 postition patterns are also supported, the leftmost position then represents minutes.&lt;/li&gt;
 &lt;li&gt;Hundreds of schedules tested and confirmed working as expected.&lt;/li&gt;
 &lt;li&gt;A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.&lt;/li&gt;
-&lt;li&gt;Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using &lt;a href=&#34;https://butler.ptarmiganlabs.com/docs/reference/rest-api&#34;&gt;Butler&amp;rsquo;s API&lt;/a&gt;. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.&lt;/li&gt;
+&lt;li&gt;Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using &lt;a href=&#34;https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/&#34;&gt;Butler&amp;rsquo;s API&lt;/a&gt;. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;The two supported schedule formats look like this:&lt;/p&gt;
 &lt;pre&gt;&lt;code&gt;    ┌───────────── seconds (0 - 59)

diff --git a/docs/docs/concepts/key-value/index.html b/docs/docs/concepts/key-value/index.html
@@ -470,7 +470,7 @@ <h4 class="alert-heading">Remember</h4>
 </div>
 
 <p>There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair&rsquo;s last update.</p>
-<p>The <a href="/docs/reference/rest-api">API docs</a> shows what methods are available to work with KV pairs.</p>
+<p>The <a href="/docs/reference/rest-api-1/">API docs</a> shows what methods are available to work with KV pairs.</p>
 <h2 id="how-can-a-key-value-store-be-used-in-sense-apps">How can a key-value store be used in Sense apps?</h2>
 <p>As mentioned above - A KV store can be useful whenever you need to stash data away for a while and then get it back. I.e. keeping track of the state of something.</p>
 <p>For example</p>

diff --git a/docs/docs/concepts/key-value/printview/index.html b/docs/docs/concepts/key-value/printview/index.html
@@ -123,7 +123,7 @@ <h4 class="alert-heading">Remember</h4>
 </div>
 
 <p>There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair&rsquo;s last update.</p>
-<p>The <a href="/docs/reference/rest-api">API docs</a> shows what methods are available to work with KV pairs.</p>
+<p>The <a href="/docs/reference/rest-api-1/">API docs</a> shows what methods are available to work with KV pairs.</p>
 <h2 id="how-can-a-key-value-store-be-used-in-sense-apps">How can a key-value store be used in Sense apps?</h2>
 <p>As mentioned above - A KV store can be useful whenever you need to stash data away for a while and then get it back. I.e. keeping track of the state of something.</p>
 <p>For example</p>

diff --git a/docs/docs/concepts/printview/index.html b/docs/docs/concepts/printview/index.html
@@ -564,7 +564,7 @@ <h4 class="alert-heading">Remember</h4>
 </div>
 
 <p>There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair&rsquo;s last update.</p>
-<p>The <a href="/docs/reference/rest-api">API docs</a> shows what methods are available to work with KV pairs.</p>
+<p>The <a href="/docs/reference/rest-api-1/">API docs</a> shows what methods are available to work with KV pairs.</p>
 <h2 id="how-can-a-key-value-store-be-used-in-sense-apps">How can a key-value store be used in Sense apps?</h2>
 <p>As mentioned above - A KV store can be useful whenever you need to stash data away for a while and then get it back. I.e. keeping track of the state of something.</p>
 <p>For example</p>
@@ -655,7 +655,7 @@ <h2 id="the-butler-scheduler">The Butler scheduler</h2>
 <li>5 postition patterns are also supported, the leftmost position then represents minutes.</li>
 <li>Hundreds of schedules tested and confirmed working as expected.</li>
 <li>A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.</li>
-<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
+<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api-1/">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
 </ul>
 <p>The two supported schedule formats look like this:</p>
 <pre><code>    ┌───────────── seconds (0 - 59)

diff --git a/docs/docs/concepts/scheduler/index.html b/docs/docs/concepts/scheduler/index.html
@@ -472,7 +472,7 @@ <h2 id="the-butler-scheduler">The Butler scheduler</h2>
 <li>5 postition patterns are also supported, the leftmost position then represents minutes.</li>
 <li>Hundreds of schedules tested and confirmed working as expected.</li>
 <li>A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.</li>
-<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
+<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api-1/">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
 </ul>
 <p>The two supported schedule formats look like this:</p>
 <pre><code>    ┌───────────── seconds (0 - 59)

diff --git a/docs/docs/concepts/scheduler/printview/index.html b/docs/docs/concepts/scheduler/printview/index.html
@@ -125,7 +125,7 @@ <h2 id="the-butler-scheduler">The Butler scheduler</h2>
 <li>5 postition patterns are also supported, the leftmost position then represents minutes.</li>
 <li>Hundreds of schedules tested and confirmed working as expected.</li>
 <li>A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.</li>
-<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
+<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api-1/">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
 </ul>
 <p>The two supported schedule formats look like this:</p>
 <pre><code>    ┌───────────── seconds (0 - 59)

diff --git a/docs/docs/index.html b/docs/docs/index.html
@@ -968,7 +968,7 @@ <h3 id="whats-new-in-version-40">What&rsquo;s new in version 4.0</h3>
 <p><strong>API docs</strong> using the OpenAPI/Swagger format.</p>
 </li>
 <li>
-<p>A totally <strong>re-engineered REST API</strong> that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs&hellip; which was really ugly. The downside is that this is a major breaking change! Please review the <a href="/docs/reference/rest-api">API docs</a> for details.</p>
+<p>A totally <strong>re-engineered REST API</strong> that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs&hellip; which was really ugly. The downside is that this is a major breaking change! Please review the <a href="/docs/reference/rest-api-1/">API docs</a> for details.</p>
 </li>
 </ul>
 

diff --git a/docs/docs/printview/index.html b/docs/docs/printview/index.html
@@ -2583,7 +2583,7 @@ <h3 id="whats-new-in-version-40">What&rsquo;s new in version 4.0</h3>
 <p><strong>API docs</strong> using the OpenAPI/Swagger format.</p>
 </li>
 <li>
-<p>A totally <strong>re-engineered REST API</strong> that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs&hellip; which was really ugly. The downside is that this is a major breaking change! Please review the <a href="/docs/reference/rest-api">API docs</a> for details.</p>
+<p>A totally <strong>re-engineered REST API</strong> that now better follows best practices when to use GET/POST/PUT/DELETE. Previously everything was done using GETs&hellip; which was really ugly. The downside is that this is a major breaking change! Please review the <a href="/docs/reference/rest-api-1/">API docs</a> for details.</p>
 </li>
 </ul>
 
@@ -8509,7 +8509,7 @@ <h4 class="alert-heading">Remember</h4>
 </div>
 
 <p>There is also an optional, per KV-pair Time To Live (TTL) feature. If used it will auto-delete the KV pair when a certain time has passed from the KV-pair&rsquo;s last update.</p>
-<p>The <a href="/docs/reference/rest-api">API docs</a> shows what methods are available to work with KV pairs.</p>
+<p>The <a href="/docs/reference/rest-api-1/">API docs</a> shows what methods are available to work with KV pairs.</p>
 <h2 id="how-can-a-key-value-store-be-used-in-sense-apps">How can a key-value store be used in Sense apps?</h2>
 <p>As mentioned above - A KV store can be useful whenever you need to stash data away for a while and then get it back. I.e. keeping track of the state of something.</p>
 <p>For example</p>
@@ -8600,7 +8600,7 @@ <h2 id="the-butler-scheduler">The Butler scheduler</h2>
 <li>5 postition patterns are also supported, the leftmost position then represents minutes.</li>
 <li>Hundreds of schedules tested and confirmed working as expected.</li>
 <li>A Qlik Sense task ID is associated with each schedule. When the schedule fires, the associated task is started.</li>
-<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
+<li>Schedules can be added either manually in the YAML schedules file (as defined in the main Butler config file) or using <a href="/docs/reference/rest-api-1/">Butler&rsquo;s API</a>. A sample schedule file is included in the GitHub repository. Schedules added using the API will be stored in the schedule YAML file referenced in the main Butler config file.</li>
 </ul>
 <p>The two supported schedule formats look like this:</p>
 <pre><code>    ┌───────────── seconds (0 - 59)

diff --git a/docs/index.html b/docs/index.html
@@ -194,7 +194,7 @@ <h4 class="h3">Task failure notifications</h4>
 Who was it that stopped that important 3-hour reload 5 minutes before it was done?</p>
 <p>Get notified when tasks fail or are stopped, with notifications sent to Slack, Microsoft Teams, email, InfluxDb, New Relic, Signl4 and other destinations.<br>
 Full support for HTML/Markdown formatting and 40+ template fields.</p>
-<p><a href="/docs/concepts/alert-emails/">Read more…</a></p>
+<p><a href="/docs/concepts/failed-reloads/">Read more…</a></p>
 
 </div>
 
@@ -211,7 +211,7 @@ <h4 class="h3">Save logs from failed reloads</h4>
 <p>Finding the complete logs from failed reloads can be a pain.</p>
 <p>Butler can save these for you, sorted by date.<br>
 Finding what caused a reload to fail is now easier than ever!</p>
-<p><a href="/docs/concepts/failed-reload-logs/">Read more…</a></p>
+<p><a href="/docs/concepts/failed-reloads/">Read more…</a></p>
 
 </div>
 
@@ -345,7 +345,7 @@ <h4 class="h3">App metadata extract</h4>
 <div class="mb-0">
 <p>Extract app metadata for a single or all apps in a Sense cluster.
 Great for backup purposes!</p>
-<p><a href="/docs/reference/rest-api/?operationsSorter=alpha">Read more…</a></p>
+<p><a href="/docs/reference/rest-api-1/?operationsSorter=alpha">Read more…</a></p>
 
 </div>