Skip to content

Commit d490af8

Browse files
ferkiferki
committed
Site update
1 parent 845eb60 commit d490af8

14 files changed

Lines changed: 799 additions & 325 deletions

File tree

‎2025/03/21/minimum-viable-rex/index.html‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -292,6 +292,9 @@ <h2 id="summary"><a href="#summary">Summary</a></h2>
292292
</a>
293293
</li>
294294
<li class="next">
295+
<a href="/2025/04/02/rexfile-foundations/index.html" rel="next">
296+
Newer →
297+
</a>
295298
</li>
296299
</ul>
297300

‎2025/04/02/rexfile-foundations/index.html‎

Lines changed: 376 additions & 0 deletions
Large diffs are not rendered by default.

‎index.atom‎

Lines changed: 38 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,51 @@
22
<feed xmlns="http://www.w3.org/2005/Atom">
33
<id>https://blog.ferki.it/</id>
44
<title>agile sysadmin</title>
5-
<updated>2025-03-21T00:00:00Z</updated>
5+
<updated>2025-04-02T00:00:00Z</updated>
66
<link href="https://blog.ferki.it/index.atom" rel="self" />
77
<link href="https://blog.ferki.it/" rel="alternate" />
88
<author>
99
<name>Ferenc Erki</name>
1010
</author>
1111
<generator version="0.098">Statocles</generator>
1212

13+
<entry>
14+
<id>https://blog.ferki.it/2025/04/02/rexfile-foundations/</id>
15+
<title>Rexfile foundations</title>
16+
<author><name>Ferenc Erki</name></author>
17+
<link href="https://blog.ferki.it/2025/04/02/rexfile-foundations/" rel="alternate" />
18+
<content type="html"><![CDATA[
19+
<p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
20+
Rex</a> provides a good way to start benefiting
21+
from Rex. Then sometimes we have to repeat our typical procedures. Other times
22+
it would work best if we could enable others to follow the same steps.</p>
23+
24+
<p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
25+
describe our common procedures as code through the following foundational
26+
elements:</p>
27+
28+
<ul>
29+
<li>dependencies</li>
30+
<li>configuration</li>
31+
<li>inventory</li>
32+
<li>authentication</li>
33+
<li>tasks</li>
34+
<li>arbitrary Perl code</li>
35+
</ul>
36+
37+
<p>While we may treat most elements optional depending on the use case, let’s take
38+
an initial look at each.</p>
39+
40+
<p><a href="https://blog.ferki.it/2025/04/02/rexfile-foundations/#section-2">Continue reading...</a></p>
41+
42+
<p>Tags:
43+
<a href="https://blog.ferki.it/tag/rex/">rex</a>
44+
</p>
45+
46+
]]></content>
47+
<updated>2025-04-02T00:00:00Z</updated>
48+
<category term="rex" />
49+
</entry>
1350
<entry>
1451
<id>https://blog.ferki.it/2025/03/21/minimum-viable-rex/</id>
1552
<title>Minimum Viable Rex</title>
@@ -135,37 +172,5 @@ underlying details.</p>
135172
<updated>2025-02-26T00:00:00Z</updated>
136173
<category term="rex" />
137174
</entry>
138-
<entry>
139-
<id>https://blog.ferki.it/2025/02/03/lint-early-lint-often/</id>
140-
<title>Lint early, lint often</title>
141-
<author><name>Ferenc Erki</name></author>
142-
<link href="https://blog.ferki.it/2025/02/03/lint-early-lint-often/" rel="alternate" />
143-
<content type="html"><![CDATA[
144-
<p>Wikipedia defines <a href="https://en.wikipedia.org/wiki/Lint_(software)">linting
145-
software</a> as:</p>
146-
147-
<blockquote>
148-
<p>a static code analysis tool used to flag programming errors, bugs, stylistic
149-
errors and suspicious constructs.</p>
150-
</blockquote>
151-
152-
<p>Linters play an important role to detect common mistakes fast. I often find
153-
that running them first in the build pipelines happens already too late,
154-
reducing their usefulness.</p>
155-
156-
<p>When to lint to maximize their value?</p>
157-
158-
<p><a href="https://blog.ferki.it/2025/02/03/lint-early-lint-often/#section-2">Continue reading...</a></p>
159-
160-
<p>Tags:
161-
<a href="https://blog.ferki.it/tag/linting/">linting</a>
162-
<a href="https://blog.ferki.it/tag/static-analysis/">static analysis</a>
163-
</p>
164-
165-
]]></content>
166-
<updated>2025-02-03T00:00:00Z</updated>
167-
<category term="linting" />
168-
<category term="static analysis" />
169-
</entry>
170175
</feed>
171176

‎index.html‎

Lines changed: 42 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,48 @@ <h1><a href="/">🧑‍💻 agile sysadmin</a></h1>
3333
<main>
3434
<article>
3535

36+
<header>
37+
<h1><a href="/2025/04/02/rexfile-foundations/">Rexfile foundations</a></h1>
38+
39+
<aside>
40+
<time datetime="2025-04-02" title="published">
41+
🗓 2025-04-02
42+
</time>
43+
<a href="/tag/rex/">#rex</a>
44+
</aside>
45+
46+
</header>
47+
48+
49+
<section>
50+
<p>Running ad-hoc commands as shown in <a href="/2025/03/21/minimum-viable-rex/">Minimum Viable
51+
Rex</a> provides a good way to start benefiting
52+
from Rex. Then sometimes we have to repeat our typical procedures. Other times
53+
it would work best if we could enable others to follow the same steps.</p>
54+
55+
<p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
56+
describe our common procedures as code through the following foundational
57+
elements:</p>
58+
59+
<ul>
60+
<li>dependencies</li>
61+
<li>configuration</li>
62+
<li>inventory</li>
63+
<li>authentication</li>
64+
<li>tasks</li>
65+
<li>arbitrary Perl code</li>
66+
</ul>
67+
68+
<p>While we may treat most elements optional depending on the use case, let’s take
69+
an initial look at each.</p>
70+
71+
72+
<p><a href="/2025/04/02/rexfile-foundations/#section-2">Continue reading …</a></p>
73+
</section>
74+
75+
</article>
76+
<article>
77+
3678
<header>
3779
<h1><a href="/2025/03/21/minimum-viable-rex/">Minimum Viable Rex</a></h1>
3880

@@ -177,42 +219,6 @@ <h1><a href="/2025/02/26/virtues-of-rex/">Virtues of Rex</a></h1>
177219
<p><a href="/2025/02/26/virtues-of-rex/#section-2">Continue reading …</a></p>
178220
</section>
179221

180-
</article>
181-
<article>
182-
183-
<header>
184-
<h1><a href="/2025/02/03/lint-early-lint-often/">Lint early, lint often</a></h1>
185-
186-
<aside>
187-
<time datetime="2025-02-03" title="published">
188-
🗓 2025-02-03
189-
</time>
190-
<a href="/tag/linting/">#linting</a>
191-
<a href="/tag/static-analysis/">#static analysis</a>
192-
</aside>
193-
194-
</header>
195-
196-
197-
<section>
198-
<p>Wikipedia defines <a href="https://en.wikipedia.org/wiki/Lint_(software)">linting
199-
software</a> as:</p>
200-
201-
<blockquote>
202-
<p>a static code analysis tool used to flag programming errors, bugs, stylistic
203-
errors and suspicious constructs.</p>
204-
</blockquote>
205-
206-
<p>Linters play an important role to detect common mistakes fast. I often find
207-
that running them first in the build pipelines happens already too late,
208-
reducing their usefulness.</p>
209-
210-
<p>When to lint to maximize their value?</p>
211-
212-
213-
<p><a href="/2025/02/03/lint-early-lint-often/#section-2">Continue reading …</a></p>
214-
</section>
215-
216222
</article>
217223

218224
<ul class="pager">

‎index.rss‎

Lines changed: 37 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,43 @@
66
<atom:link href="https://blog.ferki.it/index.rss" rel="self" type="application/rss+xml" />
77
<description>Blog feed of agile sysadmin</description>
88
<generator>Statocles 0.098</generator>
9+
<item>
10+
<title>Rexfile foundations</title>
11+
<link>https://blog.ferki.it/2025/04/02/rexfile-foundations/</link>
12+
<guid>https://blog.ferki.it/2025/04/02/rexfile-foundations/</guid>
13+
<description><![CDATA[
14+
<p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
15+
Rex</a> provides a good way to start benefiting
16+
from Rex. Then sometimes we have to repeat our typical procedures. Other times
17+
it would work best if we could enable others to follow the same steps.</p>
18+
19+
<p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
20+
describe our common procedures as code through the following foundational
21+
elements:</p>
22+
23+
<ul>
24+
<li>dependencies</li>
25+
<li>configuration</li>
26+
<li>inventory</li>
27+
<li>authentication</li>
28+
<li>tasks</li>
29+
<li>arbitrary Perl code</li>
30+
</ul>
31+
32+
<p>While we may treat most elements optional depending on the use case, let’s take
33+
an initial look at each.</p>
34+
35+
<p><a href="https://blog.ferki.it/2025/04/02/rexfile-foundations/#section-2">Continue reading...</a></p>
36+
37+
<p>Tags:
38+
<a href="https://blog.ferki.it/tag/rex/">rex</a>
39+
</p>
40+
41+
]]></description>
42+
<pubDate>
43+
Wed, 02 Apr 2025 00:00:00 +0000
44+
</pubDate>
45+
</item>
946
<item>
1047
<title>Minimum Viable Rex</title>
1148
<link>https://blog.ferki.it/2025/03/21/minimum-viable-rex/</link>
@@ -130,37 +167,6 @@ underlying details.</p>
130167
Wed, 26 Feb 2025 00:00:00 +0000
131168
</pubDate>
132169
</item>
133-
<item>
134-
<title>Lint early, lint often</title>
135-
<link>https://blog.ferki.it/2025/02/03/lint-early-lint-often/</link>
136-
<guid>https://blog.ferki.it/2025/02/03/lint-early-lint-often/</guid>
137-
<description><![CDATA[
138-
<p>Wikipedia defines <a href="https://en.wikipedia.org/wiki/Lint_(software)">linting
139-
software</a> as:</p>
140-
141-
<blockquote>
142-
<p>a static code analysis tool used to flag programming errors, bugs, stylistic
143-
errors and suspicious constructs.</p>
144-
</blockquote>
145-
146-
<p>Linters play an important role to detect common mistakes fast. I often find
147-
that running them first in the build pipelines happens already too late,
148-
reducing their usefulness.</p>
149-
150-
<p>When to lint to maximize their value?</p>
151-
152-
<p><a href="https://blog.ferki.it/2025/02/03/lint-early-lint-often/#section-2">Continue reading...</a></p>
153-
154-
<p>Tags:
155-
<a href="https://blog.ferki.it/tag/linting/">linting</a>
156-
<a href="https://blog.ferki.it/tag/static-analysis/">static analysis</a>
157-
</p>
158-
159-
]]></description>
160-
<pubDate>
161-
Mon, 03 Feb 2025 00:00:00 +0000
162-
</pubDate>
163-
</item>
164170
</channel>
165171
</rss>
166172

‎page/2/index.html‎

Lines changed: 36 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,42 @@ <h1><a href="/">🧑‍💻 agile sysadmin</a></h1>
3333
<main>
3434
<article>
3535

36+
<header>
37+
<h1><a href="/2025/02/03/lint-early-lint-often/">Lint early, lint often</a></h1>
38+
39+
<aside>
40+
<time datetime="2025-02-03" title="published">
41+
🗓 2025-02-03
42+
</time>
43+
<a href="/tag/linting/">#linting</a>
44+
<a href="/tag/static-analysis/">#static analysis</a>
45+
</aside>
46+
47+
</header>
48+
49+
50+
<section>
51+
<p>Wikipedia defines <a href="https://en.wikipedia.org/wiki/Lint_(software)">linting
52+
software</a> as:</p>
53+
54+
<blockquote>
55+
<p>a static code analysis tool used to flag programming errors, bugs, stylistic
56+
errors and suspicious constructs.</p>
57+
</blockquote>
58+
59+
<p>Linters play an important role to detect common mistakes fast. I often find
60+
that running them first in the build pipelines happens already too late,
61+
reducing their usefulness.</p>
62+
63+
<p>When to lint to maximize their value?</p>
64+
65+
66+
<p><a href="/2025/02/03/lint-early-lint-often/#section-2">Continue reading …</a></p>
67+
</section>
68+
69+
</article>
70+
<article>
71+
3672
<header>
3773
<h1><a href="/2024/07/25/packaging-go-dependencies-for-gentoo/">Packaging Go dependencies for Gentoo</a></h1>
3874

@@ -150,39 +186,6 @@ <h1><a href="/2024/05/01/packaging-vale-3-4-2-for-gentoo/">Packaging vale-3.4.2
150186
and extensibility in mind”, has a new <a href="https://github.com/errata-ai/vale/releases/tag/v3.4.2">v3.4.2
151187
release</a>.</p>
152188

153-
<p><a href="https://github.com/ferki/gentoo-overlay">My overlay</a> already makes it
154-
available for fellow Gentoo users. I also contributed the same ebuild to the
155-
official Gentoo <a href="https://wiki.gentoo.org/wiki/Project:GURU">GURU overlay</a>,
156-
where it should reach the reviewed branch soon.</p>
157-
158-
159-
</section>
160-
161-
</article>
162-
<article>
163-
164-
<header>
165-
<h1><a href="/2023/09/07/packaging-vale-2-28-3-for-gentoo/">Packaging vale-2.28.3 for Gentoo</a></h1>
166-
167-
<aside>
168-
<time datetime="2023-09-07" title="published">
169-
🗓 2023-09-07
170-
</time>
171-
<a href="/tag/gentoo/">#Gentoo</a>
172-
<a href="/tag/ebuild/">#ebuild</a>
173-
<a href="/tag/overlay/">#overlay</a>
174-
<a href="/tag/guru/">#GURU</a>
175-
<a href="/tag/vale/">#vale</a>
176-
</aside>
177-
178-
</header>
179-
180-
181-
<section>
182-
<p><a href="https://vale.sh">Vale</a>, the “syntax-aware linter for prose built with speed
183-
and extensibility in mind”, has a new <a href="https://github.com/errata-ai/vale/releases/tag/v2.28.3">v2.28.3
184-
release</a>.</p>
185-
186189
<p><a href="https://github.com/ferki/gentoo-overlay">My overlay</a> already makes it
187190
available for fellow Gentoo users. I also contributed the same ebuild to the
188191
official Gentoo <a href="https://wiki.gentoo.org/wiki/Project:GURU">GURU overlay</a>,

0 commit comments

Comments
 (0)