laravel4cookbook

API 130
.
You can optionally specify the template to be used in the creation of seeders, models and controllers.
you do this by providing the –template option with the path to a Mustache template file.
Unfortunately migrations do not have this option. If you find yourself using these generators often
enough, and wanting to customise the way in which new class are created; you will probably want
to take a look at this option (and the template files in vendor/way/generators/src/Way/Generators/Generators/templates).
.
You can find out more about Jeffrey Way’s Laravel 4 Generators at: https://github.com/JeffreyWay/Laravel-
4-Generators.
Binding Models To Routes
Before we can access these; we need to add routes for them:
1 Route::model("event", "Event");
2
3 Route::get("event", [
4 "as" => "event/index",
5 "uses" => "EventController@index"
6 ]);
7
8 Route::post("event", [
9 "as" => "event/store",
10 "uses" => "EventController@store"
11 ]);
12
13 Route::get("event/{event}", [
14 "as" => "event/show",
15 "uses" => "EventController@show"
16 ]);
17
18 Route::put("event/{event}", [
19 "as" => "event/update",
20 "uses" => "EventController@update"
21 ]);
22