(R)?ex Deployment & Configuration Management


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.

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:

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.



Need Help?

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

Professional support is also available.

» Home » Care » Contribute to (R)?ex

Contribute to (R)?ex

There is no company behind (R)?ex. Everything is developed by volunteers around the globe during their free time. (R)?ex is a free, open source project. Every contribution is welcome.

Get in contact

You'll find us on irc.freenode.net in the #rex channel. Just be a bit patient, it might take a few minutes until someone answers.


The success of every project is its documentation. If there is no documentation a project won't be successful. So one part where you can help is writing user friendly documentation. It is often hard to find a good balance between documenting new features (or removing deprecated documentation) and writing new code. So if you find outdated documentation, want to add guides, tweak the design or rewrite the complete webpage, don't hesitate to contact us. You can clone the website code from GitHub. Please read the README file on how to get the website up and running on your local machine.


If you want to contribute new functionality or fix things, you can just clone the repository on GitHub and send pull requests against the development branch. We encourage you to logically group your commits together in topic/feature branches and send a pull request for each of them. We also appreciate nicely formatted and meaningful commit messages, for example something like described here. We use perltidy to help us to maintain a consequent code style throughout the project (check out our .perltidyrc for more details). We recommend setting it up with your favorite IDE or text editor, so you can apply formatting easily or even automatically to your changes before committing them. If you have any questions about how to implement something, join us on irc.freenode.net / #rex.


As mentioned above (R)?ex is completely developed by volunteers. Which means there is no guarantee that a specific feature will be released at a defined date. If you need a special feature you can sponsor it, so we can focus our efforts on that feature. In this case contact us at feature@rexify.org. Those sponsored features will also be released under the same license as (R)?ex itself. So it is guaranteed that it will remain compatible with following releases and you will also have the benefit of a community finding potential bugs or contributing enhancements.


One special case is hardware. There can't be enough hardware/environments where we can test (R)?ex. Especially given our plans about Rex.IO and rex-jobcontrol - a bare metal deployer and webfrontend for (R)?ex. If you can donate any kind of hardware please contact us at sponsor@rexify.org.

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