updated routing to fix several issues.
This commit is contained in:
Taylor Otwell
36
application/bundles.php
Normal file
36
application/bundles.php
Normal file
@@ -0,0 +1,36 @@
|
||||
<?php
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Bundle Configuration
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Bundles allow you to conveniently extend and organize your application.
|
||||
| Think of bundles as self-contained applications. They can have routes,
|
||||
| controllers, models, views, configuration, etc. You can even create
|
||||
| your own bundles to share with the Laravel community.
|
||||
|
|
||||
| This is a list of the bundles installed for your application and tells
|
||||
| Laravel the location of the bundle's root directory, as well as the
|
||||
| root URI the bundle responds to.
|
||||
|
|
||||
| For example, if you have an "admin" bundle located in "bundles/admin"
|
||||
| that you want to handle requests with URIs that begin with "admin",
|
||||
| simply add it to the array like this:
|
||||
|
|
||||
| 'admin' => array(
|
||||
| 'location' => 'admin',
|
||||
| 'handles' => 'admin',
|
||||
| ),
|
||||
|
|
||||
| Note that the "location" is relative to the "bundles" directory.
|
||||
| Now the bundle will be recognized by Laravel and will be able
|
||||
| to respond to requests beginning with "admin"!
|
||||
|
|
||||
| Have a bundle that lives in the root of the bundle directory
|
||||
| and doesn't respond to any requests? Just add the bundle
|
||||
| name to the array and we'll take care of the rest.
|
||||
|
|
||||
*/
|
||||
|
||||
return array();
|
||||
@@ -97,35 +97,6 @@ return array(
|
||||
|
||||
'timezone' => 'UTC',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Bundle Options
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify options related to application bundles, such as the
|
||||
| amount of time the bundle manifest is cached. Each option is detailed
|
||||
| below with suggestions for sensible values.
|
||||
|
|
||||
| Cache:
|
||||
|
|
||||
| All bundles have a "bundle.info" file which contains information such
|
||||
| as the name of a bundle and the URIs it responds to. This value is
|
||||
| the number of minutes that bundle info is cached.
|
||||
|
|
||||
| Auto:
|
||||
|
|
||||
| You may wish to auto-start some bundles instead of lazy-loading them.
|
||||
| This is useful for debug bundles as well as bundles that are used
|
||||
| throughout your application. You may specify which bundles should
|
||||
| be auto-loaded in this array.
|
||||
|
|
||||
*/
|
||||
|
||||
'bundle' => array(
|
||||
'cache' => 0,
|
||||
'auto' => array(),
|
||||
),
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Class Aliases
|
||||
@@ -168,6 +139,7 @@ return array(
|
||||
'Redis' => 'Laravel\\Redis',
|
||||
'Request' => 'Laravel\\Request',
|
||||
'Response' => 'Laravel\\Response',
|
||||
'Route' => 'Laravel\\Routing\\Route',
|
||||
'Router' => 'Laravel\\Routing\\Router',
|
||||
'Schema' => 'Laravel\\Database\\Schema',
|
||||
'Section' => 'Laravel\\Section',
|
||||
|
||||
@@ -7,7 +7,7 @@ class Base_Controller extends Controller {
|
||||
*
|
||||
* @param string $method
|
||||
* @param array $parameters
|
||||
* @return Laravel\Response
|
||||
* @return Response
|
||||
*/
|
||||
public function __call($method, $parameters)
|
||||
{
|
||||
|
||||
@@ -12,32 +12,57 @@
|
||||
|
|
||||
| Let's respond to a simple GET request to http://example.com/hello:
|
||||
|
|
||||
| Router::register('GET /hello', function()
|
||||
| Route::get('hello', function()
|
||||
| {
|
||||
| return 'Hello World!';
|
||||
| });
|
||||
|
|
||||
| You can even respond to more than one URI:
|
||||
|
|
||||
| Router::register('GET /hello, GET /world', function()
|
||||
| Route::post('hello, world', function()
|
||||
| {
|
||||
| return 'Hello World!';
|
||||
| });
|
||||
|
|
||||
| It's easy to allow URI wildcards using (:num) or (:any):
|
||||
|
|
||||
| Router::register('GET /hello/(:any)', function($name)
|
||||
| Route::put('hello/(:any)', function($name)
|
||||
| {
|
||||
| return "Welcome, $name.";
|
||||
| });
|
||||
|
|
||||
*/
|
||||
|
||||
Router::register(array('GET /', 'GET /home'), function()
|
||||
Route::get('/, home', function()
|
||||
{
|
||||
return View::make('home.index');
|
||||
});
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Application 404 & 500 Error Handlers
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| To centralize and simplify 404 handling, Laravel uses an awesome event
|
||||
| system to retrieve the response. Feel free to modify this function to
|
||||
| your tastes and the needs of your application.
|
||||
|
|
||||
| Similarly, we use an event to handle the display of 500 level errors
|
||||
| within the application. These errors are fired when there is an
|
||||
| uncaught exception thrown in the application.
|
||||
|
|
||||
*/
|
||||
|
||||
Event::listen('404', function()
|
||||
{
|
||||
return Response::error('404');
|
||||
});
|
||||
|
||||
Event::listen('500', function()
|
||||
{
|
||||
return Response::error('500');
|
||||
});
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Route Filters
|
||||
|
||||
@@ -1,5 +1,24 @@
|
||||
<?php
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Auto-Loader Mappings
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Laravel uses a simple array of class to path mappings to drive the class
|
||||
| auto-loader. This simple approach helps avoid the performance problems
|
||||
| of searching through directories by convention.
|
||||
|
|
||||
| Registering a mapping couldn't be easier. Just pass an array of class
|
||||
| to path maps into the "map" function of Autoloader. Then, when you
|
||||
| want to use that class, just use it. It's simple!
|
||||
|
|
||||
*/
|
||||
|
||||
Autoloader::map(array(
|
||||
'Base_Controller' => path('app').'controllers/base.php',
|
||||
));
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Auto-Loader PSR-0 Directories
|
||||
@@ -18,24 +37,4 @@
|
||||
Autoloader::psr(array(
|
||||
path('app').'models',
|
||||
path('app').'libraries',
|
||||
));
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Auto-Loader Mappings
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Laravel uses a simple array of class to path mappings to drive the class
|
||||
| auto-loader. This simple approach helps avoid the performance problems
|
||||
| of searching through directories by some kind of convention. It also
|
||||
| gives you the freedom to organize your application how you want.
|
||||
|
|
||||
| Registering a mapping couldn't be easier. Just pass an array of class
|
||||
| to path maps into the "map" function of Autoloader. Then, when you
|
||||
| want to use that class, just use it. It's a piece of cake.
|
||||
|
|
||||
*/
|
||||
|
||||
Autoloader::map(array(
|
||||
'Base_Controller' => path('app').'controllers/base.php',
|
||||
));
|
||||
Reference in New Issue
Block a user