This entry is part 1 of 1 in the series Laravel Spark. This is the first post in the series. As Pulse Storm (the small boutique software consultancy I started and continue to operate) takes a half step back from ecommerce and shifts back into software systems consulting, I’ve found myself doing a lot of initial application [...]
astorm
Last time we finished up our look at Laravel 4.2's autoloader implementation. Like a lot of features in Laravel, (or any framework), once you pull out the microscope sharp edges begin to jut out everywhere.
astorm
Pop quiz hotshot! You've put in a long day of programming. Your data models are complete, the prototype UI is done. You're going to end the day creating a simple Laravel command. You run command:make
astorm
Last time we said we'd be wrapping up our series on the Laravel 4.2 autoloader. Apparently we were fibbing, because I just realized we've failed to cover a key concept in Laravel autoloading, and one that would be impossible to shoe horn into
astorm
This one's a quick article to transition us from Composer back into Laravel. Also, in a rare bit of timely news, the Laravel core team just released Laravel 5.0. This release features some really big new features (a task runner!), promotion of
astorm
We're jumping in mid-steam this week, so be sure to catch the first half of this article, as well as the initial article that kicked off the series.
astorm
Today we're going to veer slightly away from Laravel, and take a look at Composer's autoloading features. While Composer bills itself as a "Dependency Manager", its real strength is that it gives PHP developers a standard environment to build their applications in.
astorm
PHP, the language, leaves a lot to be desired when it comes to sharing and organizing your code in a project. This problem goes back to PHP's roots, and the choice not to include a python or ruby like module system. Over the years
astorm
So far in this series we've stayed pretty focused on core Laravel concepts and their underlying implementation. However, this week we're going to go slightly farther afield and discuss some of the static method meta-programming used by Laravel's "Eloquent" ORM.
astorm
Consider the Laravel caching facade. Laravel lets you store and retrieve values to/from the cache with the following syntax
astorm
Another quick primer this week, but this time it's Laravel specific.
astorm
It's another quick primer this time. Today we're going to talk about a PHP 5.4+ feature called traits. While Laravel doesn't make heavy use of traits they are sprinkled around the core codebase, so you'll want to get familiar with them.
astorm
Last time we described the PHP patterns used to implement Laravel's facade feature, and started to describe some of the "gotchas" involved. We briefly discussed how a facade introduces a second type of singleton/shared service into the system, as well as the inherent problem
astorm
So far in this series, whenever we've wanted to use a service, we've fetched Laravel's application/service-container object with the global app function
astorm
Subtitle: PHP Has Mysterious Ways. This week it's another quick primer on PHP's lesser known "magic" features in preparation of moving on to Laravel Facades.
astorm
Last time we discussed instantiating objects in Laravel using the make method. Today we're going to talk about services, service containers, and binding objects into service containers.
astorm
This week's a quick remedial primer on PHP's ArrayAccess interface. We'll be back to Laravel next time, and promise you'll see why we needed the primer.
astorm
Laravel is already a well documented system. The quick-start guide guide has all the information a developer needs to start building applications with Laravel. What's less well documented, and more interesting to me, is documentation of Laravel's implementation. The PHP community has a pretty
astorm