Laravel Community Tools by Tighten

Category "Configuration" tricks

45 tricks
It truncates all tables and then it runs all seeders available.
kostaspt 12 years ago 17276
Sometimes you need to use some packages only in your local environment, like for debug purposes. You can include service providers in your local configuration file app/config/local/app.php. You have to worry about indexes since if you just paste service provider, it will overwrite one with same index in original configuration.
lazychaser 12 years ago 8981
I have a legacy system that uses SHA1 for passwords as opposed to bcrypt, which is used by Laravel. For now, I need people to be able to access through both systems. I use the auth.attempt event to handle password conversion.
madshadow 12 years ago 14920
Do not trust the client. Safe way to get CSRF token for use in Angular JS. Keeps it as a constant.
xtrasmal 12 years ago 42035
When you're into making an API, you may wish to make the format of the responses you provide dynamic. If you're not using controllers, you would make a class, but if you use controllers, it's a pretty good idea to place it in the base controller. As well you may restructure your response data to include more fields, e.g. for testing purposes you may wish to also include some custom debug.
vlakarados 12 years ago 13850
Nice quick one-liner to prep your system for superquick installs using the new PHP Archive installer in Laravel 4.1. More details in the blog post: http://bit.ly/1mt4Weu
dshoreman 12 years ago 8734
4.1
Laravel 4 have a lot of features some hidden :) for some developers, i found the option to run artisan commands from route or controller, like Artisan::call('migrate:install'); or Artisan::call('migrate', [ '--path'=>'app/database/migrations' ]); Artisan::call('db:seed'); it is usefull when you don't have access to the console in share hosting environments.
Bradley 12 years ago 87479
4.0
Sometimes the compiled file could get corrupted and not function properly, breaking your Laravel installation. This is a list of steps you could use trying to fix a Laravel installation that previously worked just fine on a server.
msurguy 12 years ago 8668
This is a laravel command i wrote to handle the upgrade to 4.1 It covers everything in the upgrade doc except for handling missing method. It should be easily addable if you need it. Make sure to add the following to start/artisan.php Artisan::add(new UpgradeCommand); Artisan::resolve('UpgradeCommand'); Once finished, run the following php artisan auth:reminders-controller
stygian 12 years ago 11527
4.0