laravel4cookbook

Deployment 75
70 InputOption::VALUE_OPTIONAL,
71 'An example option.',
72 null
73 ),
74 );
75 }
76
77 }
.
This file should be saved as app/commands/FooCommand.php.
There are a few things of importance here:
1. The $name property is used both to describe the command as well as invoke it. If we change
it to foo, and register it correctly (as we’ll do in a moment), then we would be able to call it
with: php artisan foo
2. The description property is only descriptive. When all the registered command are displayed
(by a call to: php artisan) then this description will be shown next to the name of the
command.
3. The fire() method is where all the action happens. If you want your command to do anything;
there is where it needs to get done.
4. The getArguments() method should return an array of arguments (or parameters) to the
command. If our command was: php artisan foo bar, then bar would be an argument.
Arguments are named (which we will see shortly).
5. The getOptions() method should return an array of options (or flags) to the command. If out
command was: php artisan foo –baz, then –baz would be an option. Options are also named
(which we will also see shortly). This file gives us a good starting point from which to build
our own set of commands.
We begin our commands by creating the EnvironmentCommand class: