Platforms overview¶
A platform is the base image a source-files deploy builds on. It brings the language runtime and a
/var/lib/tsuru/deploy script that installs your dependencies and, where needed, compiles your code.
When you run tsuru app deploy -a <app> ., deploy-agent copies your files on top of the platform
image and runs that script (see Deploying). Apps deployed with
--dockerfile or --image do not use a platform at all.
Platforms are installed by administrators with tsuru platform add <name>
(Managing platforms); tsuru platform list shows the ones
available on your installation. The official images live in
tsuru/platforms and are published to Docker Hub as tsuru/<name>.
Every one is based on tsuru/base-platform (Ubuntu), except buildpack which is based on
herokuish.
Official platforms¶
| Platform | Picks the runtime version from | Installs dependencies from | Notes |
|---|---|---|---|
go |
GO_VERSION env var, then the go directive in go.mod (closest stable match), else latest |
go mod download |
guide; default Procfile web: ./tsuru-app |
python |
Pipfile.lock > poetry.lock > uv.lock > PYTHON_VERSION > .python-version > latest 3.x |
poetry.lock, uv.lock, Pipfile.lock, requirements.txt or setup.py |
guide |
nodejs |
.nvmrc > .node-version > engines.node in package.json > current LTS |
yarn.lock (yarn) else package.json (npm) |
guide |
static |
n/a (nginx from Ubuntu, NGINX_PKG selects the flavour) |
none | serves the deployed directory; guide |
ruby |
RUBY VERSION in Gemfile.lock > .ruby-version > platform default |
Gemfile via bundler |
RUBY_REPO, GEM_SOURCE env vars for mirrors |
java |
platform image | pom.xml via maven, or a prebuilt jar |
default Procfile starts Tomcat; JAVA_MAX_MEMORY |
php |
php.version in tsuru.yaml |
composer.json when php.composer is true |
frontend apache/nginx, interpreter fpm/mod_php, php.extensions list |
perl |
platform image | cpanfile.snapshot > cpanfile via carton |
|
lua |
platform image | tsuru-1.0-1.rockspec via luarocks |
|
ballerina |
platform image | bal build |
|
buildpack |
detected by the buildpack | Heroku buildpacks through herokuish | for stacks without a dedicated platform |
scratch |
n/a | none | bare Ubuntu, for shipping prebuilt binaries with a Procfile |
Each platform's README in the repository is the authoritative description of its environment variables, files and the runtime versions it ships.
What every platform supports¶
- Procfile and tsuru.yaml as described in Procfile and tsuru.yaml.
The deploy script copies a default Procfile when your code has none and
tsuru.yamlhas noprocesses:. requirements.apt: a list of Ubuntu packages, one per line, installed withapt-getbefore the platform's own steps.repositories.aptadds extra APT sources first. Both are handled bybase-platform, so they work on every platform above exceptbuildpack.- Build hooks:
hooks.buildentries from tsuru.yaml run after the platform script. - Env vars at build time: your app's environment variables are available to the deploy script,
which is how the
*_VERSIONand mirror variables in the table are read.