(R)?ex Deployment & Configuration Management

News

2019-07-02
Deprecating official Rex packages

As part of our efforts to simplify maintenance around RexOps projects, we have decided to stop building Rex packages on our side. We recommend relying on OS packages maintained by the various distributions in their respective upstream repositories, or to install Rex from CPAN.

2019-06-09
Post-migration updates & clean-up

Over the course of the past weeks many clean-ups have been done, reaping the benefits provided by our new Statocles-based site:

2019-05-19
New site engine for rexify.org

After months of work on a new site backend, we reached the MVP today for our site to be switched over to a new engine: from now on, our site will be maintained using the static site generator Statocles.

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

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