(R)?ex the friendly automation framework



The Rex-1.13.3 release is now available on CPAN. It contains documentation updates, and a fix for debconf parsing. Behind the scenes, CI was migrated over to GitHub Actions as well.


The Rex-1.13.2 release is now available on CPAN. It contains only documentation updates, mostly for the built-in template capabilities, but also fixes a few typos.


Happy 10th birthday, Rex!

The Rex-1.13.1 release is now available on CPAN. It is focusing on CMDB bugfixes and documentation, while also fixing a missing feature flag. Upgrade is recommended for all users.


The Rex-1.13.0 release is now available on CPAN. It adds on_no_change hooks for file management commands to trigger further actions when files are left unchanged. Upgrade is recommended for all users.


The Rex-1.12.2 release is now available on CPAN. It fixes various regressions, as well as bugs around file management. Upgrade is highly recommended for all users.


Learning automation using Rex

Ferenc Erki (FErki) will be the guest of Gábor Szabó on the next Code Maven live stream to learn about automation using Rex. Register for the free event via Code Maven or Meetup, and join the discussion!

Unexpected use cases with Rex

Unexpected use cases with Rex at the 22nd German Perl/Raku Workshop 2020 in Erlangen by Ferenc Erki (FErki).

Rex & Friends

Rex & Friends talk at the Barcelona Perl & Friends 2019 by Ferenc Erki (FErki).

» Home » Docs » Release notes » Release notes for 0.33

Release notes for 0.33


# new task prepare => make {
<span class="hljs-comment"># do something</span><span class="hljs-comment">


# old task "prepare", group => "foo", sub { # do something };

# new task "prepare", group => "foo", make { # do something };

User Management


use Template;

set template_function => sub { my ( $content, $vars ) = @_; my $t = Template->new; my $out; $t->process( \$content, $vars, \$out ); return $out; };

task foo => sub { file "/etc/foo/service.conf", content => template( "service.conf.tpl", name => "foo", port => 1903 ); };


It is now easier to write independent modules. There is no break in compatibility. Both ways will work. But we suggest to rewrite/move your files.

Old-way module structure:

New module structure:

Converting an old module

It is easy to convert an old module. For the example from above, you just have to move the file "lib/Apache.pm" to "lib/Apache/Module.pm" (no code changes needed). And move the templates to "lib/Apache/templates".

Proudly powered by Statocles

GitHub / IRC / Twitter / Google Groups / StackShare / Mailing list / Server Fault   -.ô.-   Disclaimer