(R)?ex the friendly automation framework

News

2020-07-05
Rex-1.12.0

The Rex-1.12.0 release is now available on CPAN. It adds support for local rsync operations, improves tab completion for Bash and Zsh, and fixes related bugs. It also discontinues support for running Rex on Windows 7, Windows Server 2008 R2, and older versions since both mainstream and extended support has already ended for these products.

2020-06-09
Rex on StackShare

Thanks to the support from their amazing team, Rex is now listed on StackShare.

2020-06-05
Rex-1.11.0

The Rex-1.11.0 release is now available on CPAN. It enhances the behaviour of sysctl and file management, fixes bugs about group management and OpenSSH connection options, and clarifies quite a bit of documentation.

2020-05-05
Rex-1.10.0

The Rex-1.10.0 release is now available on CPAN (changelog). Apart from documentation updates and bug fixes, it adds initial package glob support, and an on_change hook for the mkdir command.

2020-04-05
Rex-1.9.0

The Rex-1.9.0 release is now available on CPAN, and it adds a new feature flag to force writing UTF-8 encoded files, documents configuration options, and fixes bugs.

Conferences

2016-06-21

Need Help?

Rex is a pure open source project, you can find community support in the following places:

Professional support is also available.

» Home » Docs » Release notes » Release notes for 0.43

Release notes for 0.43

Common

Inventory cache

If you want to cache the inventory and to use this cache for subsequent rex calls, you can use the REX_CACHE_TYPE environment variable.

REX_CACHE_TYPE=YAML rex $task

This will create a folder ".cache" and creates a separate cache file for each host. If you want to use a different folder you can set it in the REX_CACHE_PATH environment variable.

You can also set the cache type inside your Rexfile

# Rexfile
⁠user "root";
⁠password "...";
⁠cache "YAML";

It is also possible to create custom cache classes. For example if you want to save the inventory cache inside a database. Just take a look at Rex::Interface::Cache::YAML to see how it is implemented.

Reporting of changes

If you want to get a report of the changes Rex had done on your systems, you can use the new reporting feature.

Currently not every Rex function gets monitored by this feature, but all important ones are. This feature will be extended with version 2 of rex.

To activate the reporting you can use the REX_REPORT_TYPE environment variable or use the reporting feature inside your Rexfile.

REX_REPORT_TYPE=YAML rex the-task

Or, within the Rexfile

# Rexfileuse Rex -base;
⁠report -on => "YAML";

The YAML report will be created inside a directory called report. If you want to use a different directory you can set it with a special variable.

use Rex -base;
⁠report -on      => "YAML";
⁠set report_path => "/path/to/";

It is also possible to create custom reporting classes. Just take a look at Rex::Report::RexIO.

New CLI commands to better integrate Rex into your shell scripts

With these commands it is easy to use Rex from within a shell script.

You can test these scripts by checking out the krimdomu/rex-shell-extension GitHub repository.

Login to fe01.my.lan and execute uptime

#!/bin/bash
export REX_REMOTE_HOST="fe01.my.lan"
GROUPS=$(rex-run "id -Gn www-data")
for group in $GROUPS; do
    echo $group
done

Login to fe01.my.lan, testing if /etc/sudoers is there, and if not, install package and upload a template sudoers file

#!/bin/bash
export REX_REMOTE_HOST="fe01.my.lan"

if ! rex-test -f /etc/sudoers; then
   rex-install sudo
   rex-template files/sudoers.tpl | rex-upload "/etc/sudoers"
fi

Initial support for OpenWrt (FErki)

In a limited way, Rex now supports OpenWrt.

Enhancements

rex will now only upload a file if it really changes and it will upload the file into a temporary file and rename it after the upload.

Bugfixes

Proudly powered by Statocles

Google Group / Twitter / GitHub / Mailinglist / irc.freenode.net #rex   -.ô.-   Disclaimer