Downloaded 501 times
Laravel 5
- 1. Laravel 5 Brian Feaver LeadDeveloper @ WiseBanyan
- 2. About Me • LeadDeveloper at WiseBanyan • Free online financial advisor • http://wisebanyan.com • 10+ years of software development
- 3. Assumptions You know theseright? • Composer • Basic development environment • Can read documentation • http://laravel.com/docs/5.0#install-laravel
- 4. What am Icovering? • What is Laravel? • Basics of Laravel (basics of any framework ever?) • Some cool stuff about Laravel (packaged libraries and services) • Some things not-so-cool
- 5. What is Laravel? •PHP Framework for Web Artisans • Built on top of Symfony2 Components • Like any framework, provides services and libraries to make interacting with web requests and other services
- 6. The Basics • Routing •Controllers • Templating (Blade) • ORM (Eloquent)
- 7. Routing • Routes aredefined in routes.php • Basic route uses a closure • Or you can use a Controller http://laravel.com/docs/5.0/routing
- 8.
- 9. Routing with aController
- 10. Routing with aController
- 11. Route Parameters You candefine parameters within the route
- 12. Templates Laravel uses theBlade template engine Layouts http://laravel.com/docs/5.0/templates
- 13.
- 14.
- 15. Eloquent (ORM) • ActiveRecord • Table - plural, snake_case class name • Migrations • Support relationships • Soft deleting • Timestamps
- 16. Eloquent (ORM) The Bad™ •“Joins” • Uses subqueries • You can do actual joins, but you have to write them using the query builder yourself • Can cause missing information with duplicate columns • Eager loading - Model::with(‘relation’) • Runs two queries • My usual Active Record gripes…
- 17. The Cool Stuff •Artisan • Dependency Injection (Container) • Queue • Middleware • Filesystem (Storage Facade) • Encryption • Authentication
- 18. The Cool Stuff Thatreally shouldn’t be so cool…
- 19. The Cool Stuff Thatreally shouldn’t be so cool… Facades
- 20. Facades What do theylook like? Facade::doSomethingCool()
- 21. Facades What do theylook like? Facade::doSomethingCool() Isn’t that a static method? Well, no…
- 22. Facades What are they? •A “static” access to underlying service • Look like static resources, but actually uses services underneath • Can be mocked for testing (at least with Mockery… no comment)
- 23. Facades Why you shouldn’tuse them… • They hide the dependencies of the service or class using them - This is the important one! • Can be overridden, but then you override them everywhere http://programmingarehard.com/2014/01/11/stop-using-facades.html
- 24. Facades What to doinstead You can instead inject them by their underlying service class names. See: http://laravel.com/docs/5.0/facades#facade-class-reference
- 25.
- 26. Onto the coolstuff…
- 27.
- 28. Dependency Injection (Container) • App::make()- Facade… • Uses reflection to determine dependencies • Does not require any configuration • Can be configured with a ServiceProvider (PHP class)
- 29. Queue • Interface to: •Amazon SQS • IronMQ • Redis queues • Beanstalkd • sync - calls job inline http://laravel.com/docs/5.0/queues
- 30. Queue (worker) • Useartisan to consume the job in the queue • php artisan queue:work • Also provides queue:listen and --daemon for continuous workers
- 31. Middleware • Allows processingor filtering of requests entering the system • http://laravel.com/docs/5.0/middleware Encryption • Simplified encryption using mcrypt • http://laravel.com/docs/5.0/encryption
- 32. Filesystem • Abstraction layerto local and remote filesystems • Amazon S3 • FTP/SFTP • Local • Dropbox • Uses the league/flysystem library http://laravel.com/docs/5.0/filesystem
- 33. Authentication • Includes librariesto do basic username/password authentication out of the box • Includes password recovery (Forgot password?) • Protecting routes using filters http://laravel.com/docs/5.0/authentication
- 34.
- 35.