Forms are often used to interact with a specific model such as a user or a blog post. However, in many circumstances a form may collect data that is related to multiple data models.
It may also have special validation requirements that have little to do with the underlying data, such as captcha and password confirmation. Consequently, it often makes sense to create a form model.
A form model represents the data needs of a form. This may be validation alone, storing values for form select drop-downs, having custom methods to generate data for the form, or managing persistent data in a session to make multi-page forms simple.
In this video I discuss modeling forms and introduce a form base model for Laravel.
More documentation and information can be found on the project's Github page.
In this video I discuss using the Laravel source code as a valuable educational resource.
In this video I discuss the basics of embedding your application logic into Laravel's routes. We revisit the topics from the the application logic in controllers screencast and approach them a bit differently.
In this video I discuss where to put your application logic when using Laravel Controllers. I discuss registering controllers with the router, creating a route with a wildcard to send parameters to a controller action, and restful controllers.
An application will usually be deployed to many environments over its lifetime. From the team's own development environments to a staging environment to the production environment configurations will likely need to be changed.
Laravel provides a simply way to enable different configurations on a per-environment basis.
In this video I walk through the Laravel folder structure and share some of my thoughts about Laravel.