rexops / rex-recipes Goto Github PK

View Code? Open in Web Editor NEW

26.0 10.0 29.0 414 KB

Community Recipes for Rex

Perl 97.81% Smarty 0.80% Roff 1.26% Raku 0.13%

rex-recipes's Introduction

DEPRECATED

This repository is considered as a deprecated approach to collect and distribute Rex modules, and will be archived.

The main problems are:

Doesn't scale: A few people must maintain all the modules, including testing and reviews, even if they are not the authors. That proved to be an unrealistic expectation.
Disconnects authors from their code: Once a module is merged, the author loses direct maintainership of it, since they can only interact with it via pull requests. They could be granted access to directly manage this repo, therefore all modules, but that is probably not what anyone wants.

What now?

Since Rex code is just Perl code, Rex modules are best maintained and distributed in the standard Perl ways. You are encouraged to have your own repos for your own modules, ask PrePAN for feedback, and perhaps also use PAUSE to publish to CPAN.

If you need help or have questions, please contact us on our various support channels.

ARCHIVE

Everything below is considered outdated, but kept available for your reference.

WHAT'S THIS?

This is a community repository for Rex Recipes.

Everyone is invited to fork this repository and do pull requests.

USAGE

As of Rex Version 0.25 there will be a command for rexify to search and download recipes for own Rex projects.

rexify --search=mysql
rexify <projectname> [directory] --use=Rex::Database::MySQL
rexify <projectname> [directory] --use=Rex::Database::MySQL --use=Rex::Webserver::Apache ...

HOWTO CONTRIBUTE

Choose a category.

For example if you are developing a recipe for a Webserver like Apache, nginx, ... use the Webserver category. If you are developing a recipe for Usermanagement use the Category User.

You can create new categories if there is no category that suite your needs.

If you don't know which category to use, just use the "Misc" category.
I don't want to dictate style guides. Just have fun.

For reference, i use space indention with 2 spaces.

EXAMPLE RECIPE

Read the Contribute Guide on http://modules.rexify.org/contribute.

rex-recipes's People

Contributors

Stargazers

Watchers

rex-recipes's Issues

if we have a .rex/, then we can also cache rex-recipes per system and per user

in my case, I'd love to just put my rex-recipes github fork into ./rex/recipes and have it be used, that way i don't have out of date duplicates whever i have a Rexfile that uses them

Add module to easily setup and run Sparrow checks

@melezhik on #26 provided a great example rex module to setup, configure and run a sparrow plugin on remote hosts. During our IRC discussions, we decided to aim for a more general approach due to high number of sparrow plugins (i.e. writing and maintaining a separate rex module for each sparrow plugin does not scale).

The idea is to have a single Rex::Misc::Sparrow module which can handle setup/configuration of a list of Sparrow plugins provided via a config file for the task (standard CMDB and/or custom file).

Basic usage examples for the idea:

setting up everything: rex Misc:Sparrow:setup
running all checks: rex Misc:Sparrow:check

Extended ideas (to be done at a later point):

run some checks, but not all: rex Misc:Sparrow:check --plugins=check1,check2
run all checks except some: rex Misc:Sparrow:check --except=check1,check2

Rex::Webserver::nginx install task does not work.

Calling this task from another library or Rexfile does nothing.
The task is never called. It works if task name is changed (to 'install_pkg' for instance).

Rex::Lang::Java Environment variable duplication after update java

when your java system is updated, the java path (if you don't use alternatives) is changed. So this test will create a duplication entry for JAVA_HOME.
append_if_no_such_line "/etc/environment", "JAVA_HOME=$java_home";

Determine a CPAN namespace for Rex recipes

We should contact precpan to talk with them about a namespace that we can use to put recipes, plugins, extensions and other "third party" code into.

Republish existing recipes

The existing recipes in this repo probably would still be useful, so it sounds like a good idea to try and republish them elsewhere (on GitHub and/or CPAN).

I think primarily the author should be notified and asked to do it, but given a permissive enough license, a new maintainer might want to step and to take over the responsibility.

What about getting stream_run into the core?

It can be very useful to be able to print continuously from a long running task and this feels like it should be in core rather than a recipe?

Document how to create and publish a Rex extension

Before we can deprecate rex-recipes, we need to have a way for people to publish their own recipes.

Add Ruby::VersionManager support for Rex::Lang::Ruby

move the recipes into a more useful namespace.

I think the recipes should move into the Rex:: namespace.

firstly, so they won't conflict with non-rex perl modules that might be used - or worse, future CPAN modules that come into existance and then clash.

and secondly, so that when one of them becomes important enough to migrate into rex itself, no-one's code needs to change.

problem with Rex::Lang::Java meta.yml

When trying to install Java module using rexify:

rexify --use=Rex::Lang::Java

I'm getting an error message:

Getting dependencies for Rex::Lang::Java...
JSON text must be an object or array (but found number, string, true, false or null, use allow_nonref to allow this) at /usr/bin/rexify line 361.

I think the problem is related with the Rex::Lang::Java meta.yml file and the empty list of dependencies.