When you want to deploy your application on Scalingo, it needs to be built as a portable container image. This image will be loaded by our servers to run and scale your app.

A buildpack is a set of scripts which aims at:

  • Detecting the language of an application detect
  • Installing the dependencies of a project compile
  • Defining how the application should be started release

Officially Supported Buildpacks

Here is the list of officially supported buildpacks on Scalingo:

Available buildpacks for specific usage

  • Multi Buildpack - DocumentationSource - Combine different buildpacks during the deployment of your applicaiton
  • APT Buildpack - DocumentationSource
  • GraphicsMagic Buildpack - DocumentationSource - Install graphicsmagick and replace imagemagick in the container environment
  • Cairo Buildpack - DocumentationSource Install the cairo graphics library and its dependencies
  • Wkhtmltopdf Buildpack - DocumentationSource - Install wkhtmltopdf binary to generate PDF from web pages
  • Jemalloc Buildpack - DocumentationSource - Install jemalloc memory allocator library

Use a custom buildpack

We want our users to be able to use the technologies they love, we try to provide the support for an extended range of languages and frameworks, but if we don’t fit your need, you can use a custom buildpack.

Specify a precise buildpack

In some cases, your application may be detected by two different buildpacks, for instance if you are building a PHP application which manages its dependencies with grunt tasks, bower or gulp, your application will be detected as a Node.js application and not as a PHP application.

In this situation you need to specify the buildpack you want to use by defining the environment variable:


Suggest edits


©2024 Scalingo