Deploy PHP apps

PHP is available on our platform with the branches 5.6 and 7.0. You can use FTP or Git to deploy your applications.

The HTTP server is Apache 2, and the PHP code is executed by PHP-FPM.


PHP is a widely-used general-purpose scripting language that is especially suited for Web development and can be embedded into HTML.

Create an application

Refer to the page Deploy an application on Clever Cloud.


An FTP application is automatically started once the application is created, even if no code has been sent.

When you create a FTP application, a free FS Bucket add-on is provisioned, named after the application. You will find the FTP credentials in the configuration tab of this add-on.

Choose your PHP version

Since January 2016, choosing a PHP version has gotten easier: just set the PHP_VERSION environment variable to one of the following values:

  • 5.6
  • 7.0
  • 7.1

By default, all new PHP applications are created with a default PHP_VERSION, set to 5.6. You can of course change it whenever you want then redeploy your application to use the version you want.

Configuration files for PHP applications

The configuration file for your PHP application must be /clevercloud/php.json, that is a php.json file in a /clevercloud folder at the root of your application.

Change the webroot

Since one of the best practices of PHP development is to take the libraries and core files outside the webroot, you may want to set another webroot than the default one (the root of your application).

To change the webroot, just set the key webroot in the deploy part of the configuration file clevercloud/php.json with the absolute path (from the root of your application) of your new public folder.

In the following example we want to set the webroot to the folder /public:

    "deploy": {
      "webroot": "/public"

Please note the absolute path style: /public.


The change of the webroot will be rejected during the deployment if the target directory does not exist or is not a directory.

Change PHP settings

Most of PHP settings can be changed using a .user.ini file. If you want it to be used for any file and you set a different webroot than /, you need to put this file in that directory instead of the root of your repository. Please refer to the official documentation for more information. You can review the available directives; all the PHP_INI_USER, PHP_INI_PERDIR, and PHP_INI_ALL directives can be set from within user.ini.

Other settings can be changed by adding the following line in clevercloud/php.json:

      "configuration": {
         "mbstring.func_overload": 2,
         "another.setting": "value"

Here is the list of available settings:

  • mbstring.func_overload

Note: You can send a request to the support if you need to change a setting which is not in this list.

Maximum PHP Children per instance

You can fix the maximum number of PHP running processes per instance by adding the following line in clevercloud/php.json:

      "configuration": {
         "pm.max_children": 32

This setting is usefull if you need to limit the number of running processes according to the maximum connections limit of your MySQL or PostgreSQL database.

By default, pm.max_children is set to 10.

Configure Apache

We use Apache 2 as HTTP Server. In order to configure it, you can create a .htaccess file and set directives inside this file.


The .htaccess file can be created everywhere in you app, depending of the part of the application covered by directives. However, directives who applies to the entire application must be declared in a .htaccess file to the application root.


If you need basic authentication, you can use the .htpasswd file. The path to the .htpasswd of the AuthUserFile directive has to be absolute. Your site root folder is available at /var/www/bas/site/, so the directive should look like: AuthUserFile=/var/www/bas/site/.htpasswd

Define a custom HTTP timeout

You can define the timeout of an HTTP request in Apache using the HTTP_TIMEOUT environment variable.

By default, the HTTP timeout is se to 3 minutes (180 seconds).

Force HTTPS traffic

Load balancers handle HTTPS traffic ahead of your application. You can use the X-Forwarded-Proto header to know the original protocol (http or https).

Place the following snippet in a .htaccess file to ensure that your visitors only access your application through HTTPS.

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Prevent Apache to redirect HTTPS calls to HTTP when adding a trailing slash

DirectorySlash is enabled by default on the PHP scalers, therefore Apache will add a trailing slash to a resource when it detects that it is a directory.

eg. if foobar is a directory, Apache will automatically redirect to

Unfortunately the module is unable to detect if the request comes from a secure connection or not. As a result it will force an HTTPS call to be redirected to HTTP.

In order to prevent this behavior, you can add the following statements in a .htaccess file:

DirectorySlash Off
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+[^/])$          %{HTTP:X-Forwarded-Proto}://%{HTTP_HOST}/$1/  [R=301,L,QSA]

These statements will keep the former protocol of the request when issuying the redirect. Assuming that the header X-Forwarded-Proto is always filled (which is the case on our platform).

If you want to force all redirects to HTTPS, you can replace %{HTTP:X-Forwarded-Proto} with https.


We support Composer build out of the box. You just need to provide a composer.json file in the root of your repository and we will run composer.phar install for you.


If you encounter any issues, add your own composer.phar file in the root of your repository which will override the version we use.

Example of a composer.json file:

   "require": {
      "laravel/framework": "4.1.*",
      "ruflin/Elastica": "dev-master",
      "shift31/laravel-elasticsearch": "dev-master",
      "natxet/CssMin": "dev-master"
   "repositories": [
         "type": "vcs",
         "url": ""
   "autoload": {
      "classmap": [
      "psr-0": {
         "SomeApp": "app"
   "config": {
      "preferred-install": "dist"
   "minimum-stability": "dev"

Example of a minimalist PHP application using composer and custom scripts: php-composer-demo

GitHub rate limit

Sometimes, you can encounter the following error when downloading dependencies:

Failed to download symfony/symfony from dist: Could not authenticate against

To prevent this download dependencies's fails that is often caused by rate limit of GitHub API while deploying your apps, we recommend you to add oauth token in your composer configuration file or in separate file named as described in composer FAQ (API rate limit and OAuth tokens).

You can find more documentation about composer configuration at


You use Artisan to manage your project and you want to execute artisan migrate before running your app.

To do this, we use a post build hook, you have to set a new environment variable on your Clever application as following:

CC_POST_BUILD_HOOK=php artisan migrate --force

Note: You must add the execute permission to your file (chmod u+x yourfile) before pushing it.

Environment injection

Clever Cloud can inject environment variables that are defined in the dashboard and by add-ons linked to your application.

To access the variables, use the getenv function. So, for example, if your application has a postgresql add-on linked:


$dbh = new PDO(


Environment variables are displayed in the default output of phpinfo(). If you want to use phpinfo() without exposing environment variables, you have to call it this way:


Frameworks and CMS

The following is the list of tested CMS by our team.

It's quite not exhaustive, so it does not mean that other CMS can't work on the Clever Cloud platform.

Wordpress Prestashop
Dokuwiki Joomla
SugarCRM Drupal
Symfony Thelia
Laravel -

Available extensions and modules

You can check enabled extensions and versions by viewing our phpinfo() example for PHP 5.6 and PHP 7.0.

Warning: some extensions need to be enabled explicitely

The following extensions are enabled by default: imagick, memcached, memcache, mongodb, opcache, redis, solr, ssh2.

You can add DISABLE_<extension_name>: true in your environment variable to disable them.

If you have a request about modules, feel free to contact our support at


memcache and memcached extensions are not yet available for PHP 7

Enable specific extensions

Some extensions need to be enabled explicitly. To enable these extensions, you'll need to set the corresponding environment variable:

  • APC: set ENABLE_APC to true.

    APC is a framework for caching and optimizing PHP intermediate code. Warning: APC is only available for PHP 5.4.

  • APCu: set ENABLE_APCU to true.

    APCu is an in-memory key-value store for PHP. Keys are of type string and values can be any PHP variables.

  • Couchbase: set ENABLE_COUCHBASE and ENABLE_PCS to true

    Couchbase is a document database with a SQL-based query language that is engineered to deliver performance at scale.

  • IonCube: set ENABLE_IONCUBE to true.

    IonCube is a tool to obfuscate PHP code. It's often used by paying Prestashop and Wordpress plugins.

  • Mongo: set ENABLE_MONGO to true.

    MongoDB is a NoSQL Database. This extension allows to use it from PHP. Warning: this extension is now superseded by the mongodb extension. We provide it for backward compatibility.

  • NewRelic: set ENABLE_NEWRELIC to true.

    Newrelic Agent for PHP. Newrelic is a software analytics tool.

  • OAuth: set ENABLE_OAUTH to true.

    OAuth consumer extension. OAuth is an authorization protocol built on top of HTTP.

  • XDebug: set ENABLE_XDEBUG to true.

    XDebug is a debugger and profiler tool for PHP.

Use Redis to store PHP Sessions

By default, sessions are stored on a replicated file system, so that session data is available on each instance. We also provide the possibility to store the PHP sessions in a Redis database to improve performance: if your application is under heavy load, redis persistence for sessions can improve latency.

To enable this feature, you need to:

  • enable Redis support on the application (create an environment variable named ENABLE_REDIS with the value true.)
  • create and link a Redis add-on
  • create an environment variable named SESSION_TYPE with the value redis.


You must have a Redis add-on linked with your application to enable PHP session storage in Redis.
If no Redis add-on is linked with your application, the deployment will fail.

Sending e-mails

The PHP language has the mail function to directly send e-mails but we do not support it because of all the maintenance it needs. Instead, we recommend you to use Mailgun or Mailjet. These services already have everything you need to send emails from your code.

Configure Monolog

A lot of frameworks (including Symfony) use Monolog to handle logging. The default configuration of Monolog doesn't allow to log errors into the console. Here is a basic configuration of Monolog to send your application's logs into our logging system and access them into the Console:

      type:     error_log
      level:    warning

You can change the level to whatever level you desire. For Symfony, the configuration file is app/config/config_prod.yml.

Laravel doesn't need Monolog to retrieve logs via Clever console or Clever CLI. Here, ensure that you have the following line in config/app.php:

'log' => env('APP_LOG'),

Then, set APP_LOG=syslog as Clever application environment variable.

Timezone configuration

All instances on Clever Cloud run on the UTC timezone. We recommend to handle all your dates in UTC internally, and only handle timezones when reading or displaying dates.

Additionally, you can set PHP's time zone setting with .user.ini. For instance, to use the french time zone, edit .user.ini to add this line:


Header injection

Usually, you can use an .htaccess file to create / update / delete headers. You won't be able to do it from the .htaccess file if the headers come from a .php file, because php-fpm ignores the mod_headers plugin. It works fine for static files directly served by apache.

So if you need to inject headers on HTTP responses (for instance for CORS), you have to do it from PHP (you can't do it from .htaccess).

header("Access-Control-Allow-Origin: *");

If you want to keep this separate from your application, you can configure the application to execute some code on every request.

In .user.ini, add the following line (you need to create inject_headers.php first):


Deploy on Clever Cloud

Application deployment on Clever Cloud is via Git or FTP. Follow these steps to deploy your application.

Edit me on GitHub