laravel4cookbook

Deployment 77
.
This file should be saved as app/commands/EnvironmentCommand.php.
The command class begins with us setting a useful name and description for the following commands
we will create. The fire() method includes three calls to the line() method; which prints text to the
command line. The getArguments() and getOptions() methods return empty arrays because we do
not expect to handle any arguments or options.
.
You may have noticed the XML notation within the calls to the line() method. Laravel 4’s console
library extends Symphony 2’s console library; and Symphony 2’s console library allows these
definitions in order to alter the meaning and appearance of text rendered to the console.
While the appearance will be changed, by using this notation, it’s not the best thing to be doing
(semantically speaking). The bits in the comment elements aren’t comments any more than the bit
in the info elements are.
We’re simply using it for a refreshing variation in the console text colours. If this sort of jacky
behaviour offends your senses, feel free to omit the XML notation altogether!
Before we can run any commands; we need to register them with Artisan:
1 Artisan::add(new EnvironmentCommand);
.
This was extracted from app/start/artisan.php.
There’s nothing much more to say than; this code registers the command with Artisan, so that it
can be invoked. We should be able to call the command now, and it should show us something like
the following:
1 php artisan environment
2 environment:get gets host and environment.
3 environment:set adds host to environment.
4 environment:remove removes host from environment.
Congratulations! We’ve successfully created and registered our first Artisan command. Let’s go
ahead and make a few more.