ncuesta/clinner

Command execution abstraction

Clinner

, _(*1)

Clinner is a PHP 5.3+ Command-Line Interface commands execution abstraction., _(*2)

Advantages

Clinner has the following benefits:, _(*3)

• Minimalistic.
• Simple and easy to use.
• Clinner uses Composer.
• Fluent API.
• Higher-level and object oriented interface to commands.
• Command pipes, regardless of the underlying OS.
• Commands might be actual command-line executables or PHP code.
• Yes, you can mix commands and PHP code in an OO way!
• Easily extendable through Interface implementation.
• MIT Licensed.

Usage

Simple usage

The most basic use of Clinner consists of installing it as a dependency via Composer and then including Composer's autoloader.php in your code:, _(*4)

1. Create (if needed) a composer.json file or add an entry to your existing one:

    {
        "name": "my/nifty-project",

        "require": {
            "ncuesta/clinner": "dev-master"
        }
    }

1. Include Composer's autoload.php file on your code:

    <?php

        require_once __DIR__ . '/vendor/autoload.php';

1. Start using commands right away!

    <?php

        /*
         * List current working directory's files
         * and store the list as a string.
         */
        require_once __DIR__ . '/vendor/autoload.php';

        use \Clinner\Command\Command;


        $command = new Command('ls');
        $files = $command
            ->run()
            ->getOutput();
        // Or get them as an array
        $filesArray = $command->getOutputAsArray();

        if ($command->getExitCode() === 0) {
            echo 'Everything went fine.';
        } else {
            echo 'Something didn\'t work as expected...';
        }

        // There's also a factory method that allows
        // to make best use of the fluent API
        echo Command::create('ls')
            ->run()
            ->getOutput();

Passing arguments

Commands crave for arguments, so Clinner offers a way to satisfying them. By passing in a second argument to the factory method or the constructor, or using the dedicated setter method setArguments()., _(*5)

<?php

    use \Clinner\Command\Command;


    // Commands will most certainly take arguments,
    // so let's try something with them
    $command = new Command('cat', array('/etc/hosts'));
    // This will run `cat /etc/hosts`
    $command->run();

    // You might also use its factory method
    // to take even more advantage of the fluent API
    echo Command::create('cat', array('/etc/hosts'))
        ->run()
        ->getOutput();

Arguments can either be key-value pairs or just values. Key value pairs will be joined using a delimiter (see Options section for more information)., _(*6)

Options

Options allow customization of different Command behaviors. They can be passed in as a third argument for the factory method or constructor, or set via the setOptions() method., _(*7)

Currently there's only one thing that can be customized for the Command class, but it's worth noting it: you might specify the delimiter, a string that will be used to join key-value pairs of arguments. If not specified, it will default to the equals sign (=)., _(*8)

Let's see an example:, _(*9)

<?php

    use \Clinner\Command\Command;


    // `cut` command won't work if key-value pairs of arguments
    // are joined with '=':
    $command = Command::create(
        'cut',
        array(
            '-d' => ':',
            '-f' => 1,
            '/etc/passwd',
        )
    );

    $command->run();
        // => will run `cut -d=: -f=1 /etc/passwd` (WRONG)

    // Change the delimiter to '' (an empty string)
    $command->setOptions(array('delimiter' => ''));

    $command->run();
        // => will run `cut -d: -f1 /etc/passwd` (CORRECT)

Advanced usage: Commands pipes

Commands can be piped just like in any Unix shell. The basics of command pipes is that the output of a command is sent to the one that is piped to it., _(*10)

For example, if you want to run ls -a | grep -i clinner, you can:, _(*11)

<?php

    use \Clinner\Command\Command;


    $grepCommand = Command::create('grep', array('-i', 'clinner'));
    $lsCommand   = Command::create('ls', array('-a'));

    $lsCommand
        ->pipe($grepCommand)
        ->run();

    $pipeOutput = $lsCommand->getOutput();

    // Or the same thing in an uglier but more pro way

    $pipeOutput = Command::create('ls', array('-a'))
        ->pipe(Command::create('grep', array('-i', 'clinner')))
        ->run()
        ->getOutput();

Command pipes are not limited to a number of commands, you only need at least two commands., _(*12)

See next section for a more complex example involving 3 commands in a pipeline., _(*13)

Advanced usage: Mixing PHP with commands

Apart from Command class, Clinner ships with a Callback command class that enables to mix both commands and PHP code in a command pipe. Pretty cool, huh?, _(*14)

Callback class only takes a Closure or a function reference in its constructor and then is ready to run. That Closure function will receive the command's input as its first argument and is expected to return an exit code. Any information output by the function (either via echo or print or any other output method) will be considered as the command output and will be sent to the next command in the pipe, if any., _(*15)

<?php

    use \Clinner\Command\Command;
    use \Clinner\Command\Callback;


    // Get all the usernames in the system that contain an 'a' in them
    $callbackCommand = new Callback(function($input) {
        foreach (explode("\n", $input) as $line) {
            if (false !== strchr($line, 'a')) {
                echo "$line\n";
            }
        }
    });

    $systemUsers = Command::create('cat', array('/etc/passwd'))
        ->pipe(
            Command::create('grep', array('-v' => '^#'), array('delimiter' => ' '))
        )
        ->pipe(
            Command::create('cut', array('-d' => ':', '-f' => 1), array('delimiter' => ''))
        )
        ->pipe($callbackCommand)
        ->run()
        ->getOutputAsArray("\n");

Creating commands from string

As of 0.1.2 it is possible to create a Command instance from a string, using the command as if you had written it in a CLI., _(*16)

For instance, the following command could be run on the CLI:, _(*17)

~$ cat /etc/hosts | grep localhost | tr -s "\t" " "

Would output all the lines in the /etc/hosts file that contain the string localhost with any tab (\t) indent replaced by a single blank space ()., _(*18)

This very same command can be passed as a string to \Clinner\Command\Command::fromString() and a new Command instance representing this commands chain will be returned:, _(*19)

<?php

    use \Clinner\Command\Command;


    $commandString = 'cat /etc/hosts | grep localhost | tr -s "\t" " "';
    $command = Command::fromString($commandString);

    // This is equivalent to:
    $command = Command::create('cat', array('/etc/hosts'))
        ->pipe(
            Command::create('grep', array('localhost'))
        )
        -> pipe(
            Command::create('tr', array('-s', '"\t"', '" "'))
        );

And then you can work with the newly created Command instance as usual, and pipe other Commands or even Callbacks to it., _(*20)

Requirements

The only requirement for Clinner is PHP version >= 5.3., _(*21)

Contributing

Please, feel free to fork this repo and improve it in any way you consider useful -- Pull Requests are welcome!, _(*22)