Illuminate Non-Laravel

Showing a simplest-use example for using each Illuminate component in non-Laravel applications.

Usage

At the moment, the project is divided into many directories beneath public which will each contain an index file, usually written with Slim. Navigate to that directory in your terminal and run the following to serve a web site from that directory:

$ php -S localhost:8000

Now you can visit http://localhost:8000/ in your browser to view the output of each.

Packages

Done/In Progress

• Database
• Support
• Cache
• Config
• IoC Container
• Routing
• Translation
• Encryption
• Queue
• Mail
• Session (File Driver)

Planned

• Session
• Pagination
• HTTP
• Validation
• Artisan
• Events

Contributing

A few important notes:

1. The imagined end user is a CodeIgniter developer copying the route closure directly into a project, so try to avoid using any Slim conventions and use as little code outside the closure as possible.
2. While some components would be easier to implement with a Laravel-style Application instance and a fuller bootstrap, I'd prefer we implement as many as possible without loading Laravel's Service Providers.
3. Some components will require a bootstrap, and I hope we can come up with a Best-Practice bootstrap and Laravel-style Application instance for loading Service Providers, etc.

Thanks

Thanks for explicit contributions from Jan Hartigan, Jeremy Vaught, Kayla Daniels, and anyone who's submitted PRs, and Mohammad Gufran's blog posts on Config and Routing, and the work done by Phil Sturgeon and Dan Horrigan towards this general direction. Also, of course, Taylor "Baller" Otwell.

Related

See other related projects:

• CodeIgniter Service Level by @jeremyvaught
• Slim Services by @itsgoingd
• Session Gear by @phpgearbox