Using Illuminate Config outside of Laravel 4

I'm sure that there are times when you just need to write some small project that would just be an overkill to have a full Laravel 4 installation. Today let's look at how we could use Laravel 4 Config component (or illuminate/config) on a simple one page app.

To get started just create composer.json on your project directory:

    "require": {
        "illuminate/config": "4.0.*"

Run php composer.phar install and wait till the installation is finish. Now create index.php and write the following code:


include "vendor/autoload.php";

// Configurations
$configPath = __DIR__.'/config';
$environment = 'production';

$file = new Illuminate\Filesystem\Filesystem;
$loader = new Illuminate\Config\FileLoader($file, $configPath);
$config = new Illuminate\Config\Repository($loader, $environment);

$config->get(''); // this would look for /config/app.php with an array key "name".

Wasn't that hard right?

Crunching Laravel 4 for Production Server

While this might be just a micro optimization but I would like to have Laravel 4 run with minimal running process. One easiest (or rather quickest) way is to shrink loaded service providers.

Before we start I would like to note that most illuminate components are set as protected $defer = true; which is already good but still there are times that we can run the code without them. Also do note that php artisan optimize already shrunk most of Laravel and Symfony code into a single file in bootstrap/compiled.php.

Turning off Workbench

If you don't know what a workbench, you're not using it and there no reason for it to be enabled on your live server, to disable it.

Remove 'Illuminate\Workbench\WorkbenchServiceProvider' from app/config/app.php ("provide" section) and next open up bootstrap/autoload.php to remove the following line:

| Register The Workbench Loaders
| The Laravel workbench provides a convenient place to develop packages
| when working locally. However we will need to load in the Composer
| auto-load files for the packages so that these can be used here.

if (is_dir($workbench = __DIR__.'/../workbench'))

If you're not clear, see this commit

Artisan commands service providers

Artisan service providers are great, when running on command line. So why not move registering all related service providers to app/global/artisan.php.


$provides = array(

foreach ($provides as $provide)

Once you done with that, remove the provides from app/config/app.php as demonstrated in

What else?

At this point, it totally up to you. A simple app without a mail usage doesn't require Illuminate\Mail\MailServiceProvider, same could be for Illuminate\Queue\QueueServiceProvider. Give it a try and see for yourselves.

Down for Everyone, but You

I sure by now you might have been familiar with php artisan down but do you know that you can customize the configuration per requirement, for example:

  • Say that you want to make it down, except from everyone using certain IP address
  • Allow certain user to have access to the application, based on group for example.

All these feature is available directly from Laravel 4, all you need to do is edit app/start/global.php

    if (Auth::is(['Administrator'])) return null;

    return Response::make("Be right back!", 503);

Do note Auth::is() is from orchestra/auth but what important is that only administrator can access the web application when it set under maintainance mode.

Alternative Environment Detection for Laravel 4

While normally you could just use the HTTP hostname and machine name for environment detection but that isn't always great. For example what if you're sharing test environment and staging environment within the same instance? Sure you could set a different HTTP hostname for both but it still pointing to the same machine name.

Laravel 4 can be easily tweak and one method which I prefer is to add a single file that would be ignored via .gitignore such as bootstrap/environment.php, for example:


return 'local';

/* End of bootstrap/environment.php */

Add the file to .gitignore:


Now under bootstrap/start.php:

$env = $app->detectEnvironment(function ()
    return require __DIR__.'/environment.php';

And that it!

Rest API Response with Orchestra\Facile

With Laravel 4, you can create easily create Rest API response using the following code.


Route::get('users.json', function ()
    return User::all();

Route::get('users', function()
    $users = User::all();
    return View::make('users', compact('users'));

/* End of app/routes.php */

That look simple, but what if Laravel can automatically detect the request Accept header and return the response magically for you? Here come Orchestra Facile Component.


Route::get('users', function ()
    $users = User::all();
    return Facile::view('users')->with(compact('users'))->render();

/* End of app/routes.php */

Want to see it in real action?

jQuery.getJSON('', function (data) {
    var page =;


It know that if you hit the URL from a browser, return the View, and if you set Accept: application/json a json response is returned.

Laravel 4 in Shared Hosting

You might not know this but is running on a DirectAdmin based shared hosting, with no SSH access. If you ask anyone in the Laravel community most would probably suggest that you should upgrade to VPS or cloud based hosting but I always wanted to keep Orchestra Platform available everywhere.

So how did I make this happen? With DirectAdmin (or most Shared Hosting) it just a matter of relocating the public folder.

$ mv public/ public_html

Next you have to update bootstrap/paths.php to the the new path:

'public' => __DIR__.'/../public_html',

Now you can simply upload it as you would before.

- app
- bootstrap
- public_html
-- index.php
- vendor
- artisan
- server.php

Any question?

Hello World

{{ $hello_world }}

Okay, I was never been good with blog introduction nor have a good writing skill so if you're bored feel free to close this, now. I haven't really been blogging actively for awhile except for random pictures and quotes at \Debug::dump($me);, so why this?

I been focusing a lot on Orchestra Platform development but I haven't really been testing it on a real application, so yes this website is powered by Orchestra Platform 2 with Orchestra Story CMS Extension.