laravel-routing

I am building APIs for my Android app using laravel and default session driver set to REDIS. I found a good article here http://dor.ky/laravel-prevent-sessions-for-routes-via-a-filter/ which sort of serves the purpose. However when ever I hit the url it also hits the redis and generates the key which is empty. Now I want avoid creating empty session keys in redis. Ideally it should not hit the redis How can I do that? Can we customise sessios in a way so that sessions are generated only for specific routes (or disable for specific routes)? I can explain more with specific use case, please let

I am wondering if it is possible to return a relationship with laravels Route model binding ? Say is a have a user model with a relationship 'friends' to other users, and I want to return both the user info and the relationship from a route or controller. eg for the route domain.tld/user/123 Route::model('user', 'User'); Route::get('/user/{user}', function(User $user) { return Response::json($user); }); this will return me the user info fine but I also want the relationships, is there any easy/proper way to do this ? I know I can do this Route::get('/user/{user}', function((User $user) {

So, I've been able to get restful controllers working with Route::controller('users','UserController'); class UserController extends BaseController { public function getAccount(){} } and so /users/account works. However if I try to do something like Route::any('account',array('as' => 'account','uses' => 'UserController@account')); and go to /account , it doesn't work ( NotFoundHTTPException ). Is there a way to use named routes and restful controllers in conjunction? I like how the restful system breaks up requests, and how named routes encapsulate the URI's and decouple them from the function

Goal I'm trying to create Admin route restriction for my log-in users. I've tried a check to see if my user is log-in , and also if the user type is Admin , and if they are, I want to allow them access to the admin route, otherwise, respond a 404. routes.php <!-- Route group --> $router->group(['middleware' => 'auth'], function() { <!-- No Restriction --> Route::get('dashboard','WelcomeController@index'); <!-- Admin Only --> if(Auth::check()){ if ( Auth::user()->type == "Admin" ){ //Report Route::get('report','ReportController@index'); Route::get('report/create', array('as'=>'report.create',

So I'm new to the Laravel framework as of v4 and wondering what is the way to create and use RESTful controllers. Reading through the documentation, I'm a bit confused as to the difference between RESTful controllers and Resource controllers. When defining a RESTful controller, as per the docs, it suggests doing the following in routes.php : Route::controller('posts', 'PostController'); In the PostController , do we define the class methods by prefixing the name of the method with the HTTP verb we should like to use? For example: class PostController extends \BaseController { public function