Aug 25, 2014 | laravel, illuminate

"Illuminating" non-Laravel projects


This is a series of posts on Illuminate non-Laravel.

Warning: This post is over a year old. I don't always update old posts with new information, so some of this information may be out of date.

As a part of preparing for my talk at Laracon Eu, "Sharing Laravel's Best Assets With Other Projects," I planned to teach about the basics of using Illuminate components in other projects. But a small section of a 45-minute talk isn't nearly enough time to cover such a broad topic, so I decided to create a Github project called "Illuminate Non-Laravel" to teach and share more about best practices for using Illuminate components outside of Laravel.

The point of this project is to show developers, especially those working with legacy projects in frameworks like CodeIgniter, how they can use Laravel components (which are called Illuminate components) in their projects.

I want to have a simplest-use-case example for each component, with as few dependencies and as little bootstrapping as possible, but also I'd be happy to have more complicated examples and even hopefully a standard bootstrap to get a Laravel-style Application instance and Service Provider structure. (For an already-running Github project that is similar to this bootstrap I'm describing, check out Jeremy Vaught's CodeIgniter Service Level, which I haven't yet had the chance to work with.)

So, please check out the repo (mattstauffer/IlluminateNonLaravel) and watch it for the future, or if you have some experience working with this sort of stuff, please send a Pull Request to share some code.

Comments? I'm @stauffermatt on Twitter

Tags: laravel  •  illuminate

This is part of a series of posts on Illuminate non-Laravel:

  1. Aug 25, 2014 | laravel, illuminate


For quick links to fresh content, and for more thoughts that don't make it to the blog.