The aura/framework-project / aura/cli-project integrates aura/cli-kernel.
The Context object provides information about the command line environment, including any option flags passed via the command line. (This is the command line equivalent of a web request object.)
You can access the $_ENV, $_SERVER, and $argv values with the $env, $server, and $argv property objects, respectively. (Note that these properties are copies of those superglobals as they were at the time of Context instantiation.) You can pass an alternative default value if the related key is missing.
<?php
// get copies of superglobals
$env = $context->env->get();
$server = $context->server->get();
$argv = $context->argv->get();
// equivalent to:
// $value = isset($_ENV['key']) ? $_ENV['key'] : null;
$value = $context->env->get('key');
// equivalent to:
// $value = isset($_ENV['key']) ? $_ENV['key'] : 'other_value';
$value = $context->env->get('key', 'other_value');
?>The Context object provides support for retrieving command-line options and params, along with positional arguments.
To retrieve options and arguments parsed from the command-line $argv values, use the getopt() method on the Context object. This will return a GetoptValues object for you to use as as you wish.
To tell getopt() how to recognize command line options, pass an array of option definitions. The definitions array format is similar to, but not exactly the same as, the one used by the getopt() function in PHP. Instead of defining short flags in a string and long options in a separate array, they are both defined as elements in a single array. Adding a * after the option name indicates it can be passed multiple times; its values will be stored in an array.
<?php
$options = array(
'a', // short flag -a, parameter is not allowed
'b:', // short flag -b, parameter is required
'c::', // short flag -c, parameter is optional
'foo', // long option --foo, parameter is not allowed
'bar:', // long option --bar, parameter is required
'baz::', // long option --baz, parameter is optional
'g*::', // short flag -g, parameter is optional, multi-pass
);
$getopt = $context->getopt($options);
?>When we say “required” here, it means “the option, when present, must have a parameter.” It does not mean “the option must be present.” These are options, after all. If a particular value must be passed, consider using positional arguments instead.
Use the get() method on the returned GetoptValues object to retrieve the
option values. You can provide an alternative default value for when the
option is missing.
<?php
$a = $getopt->get('-a', false); // true if -a was passed, false if not
$b = $getopt->get('-b');
$c = $getopt->get('-c', 'default value');
$foo = $getopt->get('--foo', 0); // true if --foo was passed, false if not
$bar = $getopt->get('--bar');
$baz = $getopt->get('--baz', 'default value');
$g = $getopt->get('-g', []);
?>If you want alias one option name to another, comma-separate the two names. The values will be stored under both names;
<?php
// alias -f to --foo
$options = array(
'foo,f:', // long option --foo or short flag -f, parameter required
);
$getopt = $context->getopt($options);
$foo = $getopt->get('--foo'); // both -f and --foo have the same values
$f = $getopt->get('-f'); // both -f and --foo have the same values
?>If you want to allow an option to be passed multiple times, add a ‘*’ to the end of the option name.
<?php
$options = array(
'f*',
'foo*:'
);
$getopt = $context->getopt($options);
// if the script was invoked with:
// php script.php --foo=foo --foo=bar --foo=baz -f -f -f
$foo = $getopt->get('--foo'); // ['foo', 'bar', 'baz']
$f = $getopt->get('-f'); // [true, true, true]
?>If the user passes options that do not conform to the definitions, the
GetoptValues object retains various errors related to the parsing
failures. In these cases, hasErrors() will return true, and you can then
review the errors. (The errors are actually Aura\Cli\Exception objects,
but they don’t get thrown as they occur; this is so that you can deal with or
ignore the different kinds of errors as you like.)
<?php
$getopt = $context->getopt($options);
if ($getopt->hasErrors()) {
$errors = $getopt->getErrors();
foreach ($errors as $error) {
// print error messages to stderr using a Stdio object
$stdio->errln($error->getMessage());
}
};
?>To get the positional arguments passed to the command line, use the get()
method and the argument position number:
<?php
$getopt = $context->getopt();
// if the script was invoked with:
// php script.php arg1 arg2 arg3 arg4
$val0 = $getopt->get(0); // script.php
$val1 = $getopt->get(1); // arg1
$val2 = $getopt->get(2); // arg2
$val3 = $getopt->get(3); // arg3
$val4 = $getopt->get(4); // arg4
?>Defined options will be removed from the arguments automatically.
<?php
$options = array(
'a',
'foo:',
);
$getopt = $context->getopt($options);
// if the script was invoked with:
// php script.php arg1 --foo=bar -a arg2
$arg0 = $getopt->get(0); // script.php
$arg1 = $getopt->get(1); // arg1
$arg2 = $getopt->get(2); // arg2
$foo = $getopt->get('--foo'); // bar
$a = $getopt->get('-a'); // 1
?>If a short flag has an optional parameter, the argument immediately after it will be treated as the option value, not as an argument.
The Stdio object allows you to work with standard input/output streams. (This is the command line equivalent of a web response object.)
It defaults to using php://stdin, php://stdout, and php://stderr, but you can pass whatever stream names you like as parameters to the newStdio() method.
The Stdio object methods are …
getStdin(), getStdout(), and getStderr() to return the respective Handle objects;
outln() and out() to print to stdout, with or without a line ending;
errln() and err() to print to stderr, with or without a line ending;
inln() and in() to read from stdin until the user hits enter; inln() leaves the trailing line ending in place, whereas in() strips it.
You can use special formatting markup in the output and error strings to set text color, text weight, background color, and other display characteristics. See the formatter cheat sheet below.
<?php
// print to stdout
$stdio->outln('This is normal text.');
// print to stderr
$stdio->errln('<<red>>This is an error in red.');
$stdio->errln('Output will stay red until a formatting change.<<reset>>');
?>This library comes with a Status class that defines constants for exit
status codes. You should use these whenever possible. For example, if a
command is used with the wrong number of arguments or improper option flags,
exit() with Status::USAGE. The exit status codes are the same as those
found in sysexits.h.
The Aura.Cli library does not come with an abstract or base command class to
extend from, but writing commands for yourself is straightforward. The
following is a standalone command script, but similar logic can be used in a
class. Save it in a file named hello and invoke it with
php hello [-v,--verbose] [name].
<?php
use Aura\Cli\CliFactory;
use Aura\Cli\Status;
require '/path/to/Aura.Cli/autoload.php';
// get the context and stdio objects
$cli_factory = new CliFactory;
$context = $cli_factory->newContext($GLOBALS);
$stdio = $cli_factory->newStdio();
// define options and named arguments through getopt
$options = ['verbose,v'];
$getopt = $context->getopt($options);
// do we have a name to say hello to?
$name = $getopt->get(0);
if (! $name) {
// print an error
$stdio->errln("Please give a name to say hello to.");
exit(Status::USAGE);
}
// say hello
if ($getopt->get('--verbose')) {
// verbose output
$stdio->outln("Hello {$name}, it's nice to see you!");
} else {
// plain output
$stdio->outln("Hello {$name}!");
}
// done!
exit(Status::SUCCESS);
?>Sometimes it will be useful to provide help output for your commands. With Aura.Cli, the Help object is separate from any command you may write. It may be manipulated externally or extended.
For example, extend the Help object and override the init() method.
<?php
use Aura\Cli\Help;
class MyCommandHelp extends Help
{
protected function init()
{
$this->setSummary('A single-line summary.');
$this->setUsage('<arg1> <arg2>');
$this->setOptions(array(
'f,foo' => "The -f/--foo option description",
'bar::' => "The --bar option description",
));
$this->setDescr("A multi-line description of the command.");
}
}
?>Then instantiate the new class and pass its getHelp() output through Stdio:
<?php
use Aura\Cli\CliFactory;
use Aura\Cli\Context\OptionFactory;
$cli_factory = new CliFactory;
$stdio = $cli_factory->newStdio();
$help = new MyCommandHelp(new OptionFactory);
$stdio->outln($help->getHelp('my-command'));
?>
We keep the command name itself outside of the help class, because the command name may be mapped differently in different projects.
We pass a GetoptParser to the Help object so it can parse the option defintions.
We can get the option definitions out of the Help object using
getOptions(); this allows us to pass a Help object into a hypothetical command object and reuse the definitions.
The output will look something like this:
SUMMARY
my-command -- A single-line summary.
USAGE
my-command <arg1> <arg2>
DESCRIPTION
A multi-line description of the command.
OPTIONS
-f
--foo
The -f/--foo option description.
--bar[=<value>]
The --bar option description.On POSIX terminals, <<markup>> strings will change the display
characteristics. Note that these are not HTML tags; they will be converted
into terminal control codes, and do not get “closed”. You can place as many
space-separated markup codes between the double angle-brackets as you like.
reset reset display to defaults
black black text
red red text
green green text
yellow yellow text
blue blue text
magenta magenta (purple) text
cyan cyan (light blue) text
white white text
blackbg black background
redbg red background
greenbg green background
yellowbg yellow background
bluebg blue background
magentabg magenta (purple) background
cyanbg cyan (light blue) background
whitebg white background
bold bold in the current text and background colors
dim dim in the current text and background colors
ul underline in the current text and background colors
blink blinking in the current text and background colors
reverse reverse the current text and background colors
For example, to set bold white text on a red background, add <<bold white redbg>>
into your output or error string. Reset back to normal with <<reset>>.
Aura.Cli_Kernel defines the following service objects in the Container:
aura/cli-kernel:dispatcher: an instance of Aura\Dispatcher\Dispatcheraura/cli-kernel:context: an instance of Aura\Cli\Contextaura/cli-kernel:stdio: an instance of Aura\Cli\Stdioaura/cli-kernel:help_service: an instance of Aura\Cli_Kernel\HelpServiceaura/project-kernel:logger: an instance of Monolog\\LoggerThe dependency injection Container is absolutely central to the operation of an aura framework project. Please be familiar with the DI docs before continuing.
You should also familiarize yourself with Dispatching, as well as the Aura.Cli Context, Stdio, and Status objects.
Every Aura project is configured the same way. Please see the shared configuration docs for more information.
The project automatically logs to {$PROJECT_PATH}/tmp/log/{$mode}.log. If you want to change the logging behaviors for a particular config mode, edit the related config file (e.g., config/Dev.php) file to modify the aura/project-kernel:logger service.
We configure commands via the project-level config/ class files. If a command needs to be available in every config mode, edit the project-level config/Common.php class file. If it only needs to be available in a specific mode, e.g. dev, then edit the config file for that mode.
Here are two different styles of command definition.
The following is an example of a command where the logic is embedded in the dispatcher, using the aura/cli-kernel:context and aura/cli-kernel:stdio services along with standard exit codes. (The dispatcher object name doubles as the command name.)
<?php
namespace Aura\Famework_Project\_Config;
use Aura\Di\Config;
use Aura\Di\Container;
class Common extends Config
{
// ...
public function modifyCliDispatcher(Container $di)
{
$context = $di->get('aura/cli-kernel:context');
$stdio = $di->get('aura/cli-kernel:stdio');
$dispatcher = $di->get('aura/cli-kernel:dispatcher');
$dispatcher->setObject(
'foo',
function ($id = null) use ($context, $stdio) {
if (! $id) {
$stdio->errln("Please pass an ID.");
return \Aura\Cli\Status::USAGE;
}
$id = (int) $id;
$stdio->outln("You passed " . $id . " as the ID.");
}
);
}
?>You can now run the command to see its output.
cd {$PROJECT_PATH}
php cli/console.php foo 88
(If you do not pass an ID argument, you will see an error message.)
You can migrate from a micro-controller style to a full-stack style (or start with full-stack style in the first place).
First, define a command class and place it in the project src/ directory.
<?php
/**
* {$PROJECT_PATH}/src/App/Command/FooCommand.php
*/
namespace App\Command;
use Aura\Cli\Stdio;
use Aura\Cli\Context;
use Aura\Cli\Status;
class FooCommand
{
public function __construct(Context $context, Stdio $stdio)
{
$this->context = $context;
$this->stdio = $stdio;
}
public function __invoke($id = null)
{
if (! $id) {
$this->stdio->errln("Please pass an ID.");
return Status::USAGE;
}
$id = (int) $id;
$this->stdio->outln("You passed " . $id . " as the ID.");
}
}
?>Next, tell the project how to build the FooCommand through the DI
Container. Edit the project config/Common.php file to configure the
Container to pass the aura/cli-kernel:context and aura/cli-kernel:stdio service objects to
the FooCommand constructor. Then put the App\Command\FooCommand object in the dispatcher under the name foo as a lazy-loaded instantiation.
<?php
namespace Aura\Famework_Project\_Config;
use Aura\Di\Config;
use Aura\Di\Container;
class Common extends Config
{
public function define(Container $di)
{
$di->set('aura/project-kernel:logger', $di->newInstance('Monolog\Logger'));
$di->params['App\Command\FooCommand'] = array(
'context' => $di->lazyGet('aura/cli-kernel:context'),
'stdio' => $di->lazyGet('aura/cli-kernel:stdio'),
);
}
// ...
public function modifyCliDispatcher(Container $di)
{
$dispatcher = $di->get('aura/cli-kernel:dispatcher');
$dispatcher->setObject(
'foo',
$di->lazyNew('App\Command\FooCommand')
);
}
?>You can now run the command to see its output.
cd {$PROJECT_PATH}
php cli/console.php foo 88
(If you do not pass an ID argument, you will see an error message.)