Recent tricks

There are three components to generating a Facade: 1 - The wanna be Facade Class, (the class that needs to become a facade). 2 - The Facade required Class, (which tells Laravel which registered class it pertains to) 3 - A Service Provider, (which registers the Facade class in the App container)

Hello ! I'm trying to publish an application on an IIS server where my application is in a subfolder. However when trying to enter it's giving me the following error: NotFoundHttpException Application.php line in 1105 : I ran a dd () on routes and printed on the screen normally. I do not know what might be happening . Could someone help me ?

Displaying different module/package dashboard widgets using view composers.

Playing with Laravel Lumen: simple RESTful trait.

Blade's path syntax is a little odd - it uses dots instead of slashes, and always requires you to start your paths from the views root. This Blade extension allows you to pass paths with slashes, and correctly resolves parent paths via the traditional ../ syntax. Lastly, the quoting of paths is optional.

If you know what nested sets are, and use lazychazer/laravel-nestedset package, and tried his example application (https://github.com/lazychaser/nestedset-app), then here is a snippet for replace his simple nav rendering to bootstrap (3.x) navbar compatible output. (Laravel 5 solution)

If you want to add Lumen to your laravel 5 and you don't want to create new repositories models controllers etc... Just create a new Lumen project and autoload laravel namespace in lumen composer.json I assume both laravel5 and lumen are in the same directory but each one in it's own project directory.

This trait allows you to save any column from any model into a location within the storage directory to allow the column to be blade compilable with view()->file($model->getViewableColumnPath('column_name')); The trait

Once jobs have been added on the queue, we need to process them one by one. php artisan queue:listen does - It listens for jobs and runs them as they become available. But the main problem is how do we make php listen at all times ? We need to avoid having to "supervise" this process manually. This is where supervisord comes in. This is the configuration file to be placed in the /etc/supervisor/conf.d/ directory, which will create a supervisor program called "queue" which will monitor and make sure the php artisan queue:listen --tries=3 is always running.