Site update

Author: ferki

2023/08/11/local-management-with-rex/index.html

@@ -97,7 +97,9 @@ <h2 id="basic-anatomy-of-rex-task-definitions"><a href="#basic-anatomy-of-rex-ta
 <p>I’ll not go into all details here to allow us staying aware of further
 internals while focusing on the general approach.</p>
 
-<h2 id="tasks-without-an-explicit-target"><a href="#tasks-without-an-explicit-target">Tasks without an explicit target</a></h2>
+    </section>
+    <section id="section-3">
+        <h2 id="tasks-without-an-explicit-target"><a href="#tasks-without-an-explicit-target">Tasks without an explicit target</a></h2>
 
 <p>Tasks without any explicit target get executed on the local machine directly:</p>
 
@@ -125,7 +127,9 @@ <h2 id="tasks-without-an-explicit-target"><a href="#tasks-without-an-explicit-ta
 task)</a>
 section in the documentation.</p>
 
-<h2 id="tasks-targeting-local-explicitly"><a href="#tasks-targeting-local-explicitly">Tasks targeting <code>&lt;local&gt;</code> explicitly</a></h2>
+    </section>
+    <section id="section-4">
+        <h2 id="tasks-targeting-local-explicitly"><a href="#tasks-targeting-local-explicitly">Tasks targeting <code>&lt;local&gt;</code> explicitly</a></h2>
 
 <p>One may intentionally design a task to manage the local machine by using the
 special <code>&lt;local&gt;</code> hostname recognized by Rex:</p>
@@ -142,7 +146,9 @@ <h2 id="tasks-targeting-local-explicitly"><a href="#tasks-targeting-local-explic
 <code>-H</code> or <code>-G</code> options, or with the <code>on</code> option of
 <a href="https://metacpan.org/pod/Rex::Commands#run_task"><code>run_task</code></a> from code.</p>
 
-<h2 id="override-the-tasks-target-to-local"><a href="#override-the-tasks-target-to-local">Override the task’s target to <code>&lt;local&gt;</code></a></h2>
+    </section>
+    <section id="section-5">
+        <h2 id="override-the-tasks-target-to-local"><a href="#override-the-tasks-target-to-local">Override the task’s target to <code>&lt;local&gt;</code></a></h2>
 
 <p>The <code>-H</code> command line option supports the same special <code>&lt;local&gt;</code> hostname:</p>
 
@@ -166,7 +172,9 @@ <h2 id="override-the-tasks-target-to-local"><a href="#override-the-tasks-target-
 <p>This approach allows users to intentionally choose local execution, regardless
 of a task having an explicit target or not.</p>
 
-<h2 id="disable-ssh-per-task-with-no_ssh-task"><a href="#disable-ssh-per-task-with-no_ssh-task">Disable SSH per task with <code>no_ssh task</code></a></h2>
+    </section>
+    <section id="section-6">
+        <h2 id="disable-ssh-per-task-with-no_ssh-task"><a href="#disable-ssh-per-task-with-no_ssh-task">Disable SSH per task with <code>no_ssh task</code></a></h2>
 
 <p>The <code>no_ssh</code> command hints individual tasks to not use SSH:</p>
 
@@ -190,7 +198,9 @@ <h2 id="disable-ssh-per-task-with-no_ssh-task"><a href="#disable-ssh-per-task-wi
 <p>See also the <a href="https://metacpan.org/pod/Rex::Commands#no_ssh">no_ssh</a>
 documentation.</p>
 
-<h2 id="disable-ssh-globally-with-no_ssh"><a href="#disable-ssh-globally-with-no_ssh">Disable SSH globally with <code>no_ssh</code></a></h2>
+    </section>
+    <section id="section-7">
+        <h2 id="disable-ssh-globally-with-no_ssh"><a href="#disable-ssh-globally-with-no_ssh">Disable SSH globally with <code>no_ssh</code></a></h2>
 
 <p>In case none of the tasks need SSH to connect to their targets, the <code>no_ssh</code>
 command can disable it globally:</p>
@@ -212,7 +222,9 @@ <h2 id="disable-ssh-globally-with-no_ssh"><a href="#disable-ssh-globally-with-no
 <p>See also the <a href="https://metacpan.org/pod/Rex::Commands#no_ssh">no_ssh</a>
 documentation.</p>
 
-<h2 id="running-parts-of-a-task-within-local-blocks"><a href="#running-parts-of-a-task-within-local-blocks">Running parts of a task within <code>LOCAL{}</code> blocks</a></h2>
+    </section>
+    <section id="section-8">
+        <h2 id="running-parts-of-a-task-within-local-blocks"><a href="#running-parts-of-a-task-within-local-blocks">Running parts of a task within <code>LOCAL{}</code> blocks</a></h2>
 
 <p>Wrapping parts of the task steps in a <code>LOCAL{}</code> block forces these to run on
 the local machine instead of on the target in effect otherwise:</p>
@@ -233,7 +245,9 @@ <h2 id="running-parts-of-a-task-within-local-blocks"><a href="#running-parts-of-
 <p>See also the <a href="https://metacpan.org/pod/Rex::Commands#LOCAL">LOCAL</a>
 documentation.</p>
 
-<h2 id="connect-to-local-host-over-ssh"><a href="#connect-to-local-host-over-ssh">Connect to local host over SSH</a></h2>
+    </section>
+    <section id="section-9">
+        <h2 id="connect-to-local-host-over-ssh"><a href="#connect-to-local-host-over-ssh">Connect to local host over SSH</a></h2>
 
 <p>Using the identity of the local machine as target makes it possible to treat it
 the same way as remotes, including connecting to it using SSH like to any

2025/02/26/virtues-of-rex/index.html

@@ -165,7 +165,9 @@ <h3 id="concerned-about-using-perl"><a href="#concerned-about-using-perl">Concer
   community of users and developers.</p>
 </blockquote>
 
-<h2 id="empower-users-through-trust"><a href="#empower-users-through-trust">Empower users through trust</a></h2>
+    </section>
+    <section id="section-3">
+        <h2 id="empower-users-through-trust"><a href="#empower-users-through-trust">Empower users through trust</a></h2>
 
 <p>Silver bullets work best when the challenge involves fighting werewolves. Other
 situations tend to have more effective and less expensive solutions.</p>
@@ -314,7 +316,9 @@ <h4 id="push-and-pull"><a href="#push-and-pull">Push and pull</a></h4>
 receive hook, which executes <code>rex converge</code> upon <code>git push</code>. Don’t forget to
 use some locking to avoid overlapping execution of both, though.</p>
 
-<h2 id="enable-graceful-bootstrapping"><a href="#enable-graceful-bootstrapping">Enable graceful bootstrapping</a></h2>
+    </section>
+    <section id="section-4">
+        <h2 id="enable-graceful-bootstrapping"><a href="#enable-graceful-bootstrapping">Enable graceful bootstrapping</a></h2>
 
 <p>Getting started with automation initiatives may feel cumbersome or
 intimidating. It often involves having to convince team members and decisions
@@ -367,7 +371,9 @@ <h3 id="my-personal-getting-started-story"><a href="#my-personal-getting-started
 solutions, while staying so lightweight compared to alternatives. Ultimately
 that experience drove me to learn Modern Perl properly, and start contributing.</p>
 
-<h2 id="epilogue"><a href="#epilogue">Epilogue</a></h2>
+    </section>
+    <section id="section-5">
+        <h2 id="epilogue"><a href="#epilogue">Epilogue</a></h2>
 
 <p>These principles establish Rex, the friendly automation framework as a powerful
 alternative among infrastructure automation and configuration management

2025/03/05/installing-rex/index.html

@@ -101,7 +101,9 @@ <h2 id="install-from-cpan"><a href="#install-from-cpan">Install from CPAN</a></h
 clean working environment to use Rex, isolating it from the system’s own Perl
 installations.</p>
 
-<h2 id="use-package-managers"><a href="#use-package-managers">Use package managers</a></h2>
+    </section>
+    <section id="section-3">
+        <h2 id="use-package-managers"><a href="#use-package-managers">Use package managers</a></h2>
 
 <p>Thanks to the generous effort of package maintainers, many operating systems
 ship Rex through their own official package repositories. For a known list of
@@ -132,7 +134,9 @@ <h2 id="use-package-managers"><a href="#use-package-managers">Use package manage
 versions, please let both us and the package maintainers know, so we may figure
 out an even more streamlined delivery together.</p>
 
-<h2 id="build-from-source"><a href="#build-from-source">Build from source</a></h2>
+    </section>
+    <section id="section-4">
+        <h2 id="build-from-source"><a href="#build-from-source">Build from source</a></h2>
 
 <p>Even with publishing trial releases to CPAN during development, sometimes it
 fits best to use an unreleased version of Rex. For example:</p>
@@ -176,7 +180,9 @@ <h3 id="installation"><a href="#installation">Installation</a></h3>
 install</code></li>
 </ol>
 
-<h2 id="verifying-the-installation"><a href="#verifying-the-installation">Verifying the installation</a></h2>
+    </section>
+    <section id="section-5">
+        <h2 id="verifying-the-installation"><a href="#verifying-the-installation">Verifying the installation</a></h2>
 
 <p>After installation, check the current version with the following command:</p>
 
@@ -189,7 +195,9 @@ <h2 id="verifying-the-installation"><a href="#verifying-the-installation">Verify
 <pre><code class="highlight">$ rex <span class="synSpecial">-e</span> <span class="synOperator">&#39;</span><span class="synString">say run q(hostname)</span><span class="synOperator">&#39;</span>
 </code></pre>
 
-<h2 id="summary"><a href="#summary">Summary</a></h2>
+    </section>
+    <section id="section-6">
+        <h2 id="summary"><a href="#summary">Summary</a></h2>
 
 <p>We looked at the main options to install Rex, their similarities and
 differences, as well as how to quickly verify the results.</p>
@@ -207,6 +215,9 @@ <h2 id="summary"><a href="#summary">Summary</a></h2>
             </a>
     </li>
     <li class="next">
+            <a href="/2025/03/12/perl-basics-for-rex/index.html" rel="next">
+                Newer →
+            </a>
     </li>
 </ul>