Deploying Laravel on Scalingo


When a PHP application is deployed, we’re looking at the composer.json file to know if it is using a particular framework. For Laravel, we’re looking if the Composer dependencies contain laravel/framework. If so, your app is deployed as a Laravel application.

  "require": {
    "laravel/framework": "~4.2",
    // ....

During the deployment process you’ll see the following output, mentioning that the framework has correctly been detected.

-----> Detected Laravel App
-----> Setting up Laravel App

Database configuration

A Laravel application requires a database, often a SQL database like MySQL or PostgreSQL. This article will be using MySQL, but it should be identical with a PostgreSQL database.

First, a MySQL has to be added to your application. This addon will inject the environment variable SCALINGO_MYSQL_URL and its alias DATABASE_URL.


To use this URL in your application, add at the top of your app/config/database.php file the following lines. They decompose the URL into the different fields and let you configure your application.

$url = parse_url(getenv("DATABASE_URL"));

$host = $url["host"];
$username = $url["user"];
$password = $url["pass"];
$database = substr($url["path"], 1);

Then find the mysql entry in the database.php file and modify it like:

    'mysql' => array(
        'driver'    => 'mysql',
        'host'      => $host,
        'database'  => $database,
        'username'  => $username,
        'password'  => $password,
        'charset'   => 'utf8',
        'collation' => 'utf8_unicode_ci',
        'prefix'    => '',

Now that your application database is configured, let’s work on the migrations.


Artisan is the command-line interface included with Laravel. It provides a number of helpful commands that can assist you while you build your application.

Migrations are like version control for your database, allowing your team to modify and share the application’s database schema. Migrations are typically paired with Laravel’s schema builder to build your application’s database schema. If you have ever had to tell a teammate to manually add a column to their local database schema, you’ve faced the problem that database migrations solve.

First Migration

Creating a migration with Laravel is done with the following command on your workstation.

./artisan make:migration create_plants

The file is created at the location database/migrations/date_yourmigration. Edit it to write the content of the migration.

public function up()
    Schema::create('plants', function($table) {
        $table->string('common_name', 100);
        $table->string('latin_name', 100);

public function down()

To run locally the migration to see if the syntax is right, run the following command:

./artisan migrate

If everything went well, add this file to your Git repository and deploy the application on the platform. Once the application has been deployed, apply the migration to your production database:

scalingo --app my-app run php artisan migrate

For every migration file, a down method should be written in the case we want to rollback database migrations:

scalingo --app my-app run php artisan migrate:rollback

Another example: alter a database table.

The previous example created a ‘table creation’ migration, here is an example of table alteration.

public function up()
    Schema::table('plants', function($table) {
        $table->unique('latin_name', 'plants_unique_latin_name');

public function down()
    Schema::table('authors', function($table) {

As previously, running the migration on the hosted application once deployed:

scalingo --app my-app run php artisan migrate

For more examples, refer to the official Laravel documentation.

Apply migrations automatically after deployment

So far the action to apply migrations on the production database was manual. It is possible to automate it by using a postdeploy hook All you have to do is to create a Procfile file at the root of your project with the following content:

postdeploy: php artisan migrate

That’s it! If a deployment is a success, the command applying migrations will be automatically run.

Laravel queues

Handling Laravel queues requires you to start another process in your application. Add the following line to the Procfile of your application:

queues: php artisan queue:work --queue=high,default

The arguments of the --queue option must be customized to suit your needs. After deploying your application, you must scale the newly created type of containers queues at least to 1.

Laravel tasks scheduler

The Laravel PHP framework includes a command scheduler for asynchronous tasks. However, Laravel’s documentation states you need to add a cron entry which is not possible on Scalingo.

This documentation page guides you to let your application use the Laravel command scheduler on Scalingo. The following command must be added to your app. It calls the Laravel scheduler every minutes. It requires you to start another process in your application.


namespace App\Console\Commands;

use Carbon\Carbon;
use Illuminate\Console\Command;
use Illuminate\Support\Facades\Artisan;

class SchedulerDaemon extends Command
   * The name and signature of the console command.
   * @var string
  protected $signature = 'schedule:daemon {--sleep=60}';

   * The console command description.
   * @var string
  protected $description = 'Call the scheduler every minute.';

   * Execute the console command.
   * @return mixed
  public function handle()
      while (true) {
          $this->line('<info>[' . Carbon::now()->format('Y-m-d H:i:s') . ']</info> Calling scheduler');



Don’t forget to add the following line to the Procfile of your application:

scheduler: php artisan schedule:daemon

Based on an article on Neon Tsunami.

mode_edit Suggest edits