Switching From Windows To Linux

By Jason Lewis on the

In the past I've always done my development on Windows. At one stage I had planned to do a series on my Windows development environment but I never got around to it. What a shame.

Don't get me wrong, I never truly hated Windows, although it did have a couple of shortcomings that annoyed me but I always worked around them. Recently though I've just become tired of it. A few days ago I was getting weird results with some unit tests. No matter what I did it just wasn't working, yet at the same time it was working fine on my CentOS server.

So, I did what any sane person would do. I begun trialling a few different Linux distributions to find one I really liked.

Continue reading »

Laravel 4: Diving Into The Source

By Jason Lewis on the

Those of you that are currently using Laravel in your projects will be aware that when you make a static call like Route::get() you're actually hitting a facade. In nearly every article about facades you'll see the example of what is happening in the background, in our case it's be something like $app['router']->get().

In this article I want to talk about how you can find your way around the source. For many this can be a bit troublesome as you'll go to where you think it is but you end up somewhere else entirely.

Continue reading »

Error After A Composer Update Of The Laravel 4 Beta

By Jason Lewis on the

When you're developing an application (or anything for that matter) with a product that is deemed "not yet stable" or as it's more widely known, "beta", you should be expecting changes. I'm referring to the Laravel 4 beta but you could probably apply this article to just about any beta phase, ever.

Laravel 4 uses Composer to install its dependencies and other bits and pieces of the framework. That's just bloody wonderful. So all you have to do is composer update every now and again and you'll have the latest changes pulled in, right? Wrong! Dead wrong. That's so wrong that I'm having trouble comprehending the wrongness of it.

Continue reading »

Laravel 4: Develop Packages Using The Workbench

By Jason Lewis on the

In the early days of Laravel we were blessed with modules. Modules allowed us to separate parts of our applications into more manageable pieces. This meant that modules could contain their own controllers, routes, libraries, configuration, composers, filters, etc. When Laravel 3 was released modules were revamped and renamed to bundles. A Laravel specific bundle repository was setup and developers could publish their bundles so that others could install them with Artisan. It was a great way to easily drop code in to an existing application.

With Laravel 4 hitting beta soon many are wondering what will happen to bundles and how they'll need to be changed to be of any use. There won't be any Laravel specific bundle repository for Laravel 4 since it's now making use of Composer to handle package dependencies.

Continue reading »