scalingo.json configuration
scalingo.json configuration files
| Type | object |
|---|---|
| File match |
scalingo.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/scalingo-json-configuration/latest.json |
| Source | https://raw.githubusercontent.com/Scalingo/developers-documentation/refs/heads/master/scalingo.schema.json |
Validate with Lintel
npx @lintel/lintel check
Extracted from https://developers.scalingo.com
Properties
Complete name of the project
Description in one or two sentences of the app
Official website of the application if any
URL to the logo of the project
Location of the GIT repository of the project
Branch name or commit ID of the code to use
Name of the stack to use : https://doc.scalingo.com/platform/internals/stacks/stacks
Copy database credentials from parent app
Formation of containers when an app is created
The formation is the definition of the container which will be started once the application is deployed. (Either coming from a one-click deployment button, or a review app from the GitHub integration)
The keys of the environment object are the name of the variables you want to add.
Note: supplying null or an empty string to value will remove the variable from the environment.
It can be used to delete environment variables present in the parent app.
See https://doc.scalingo.com/platform/app/environment
The scripts.postdeploy key is now deprecated in favor of postdeploy hook in the Procfile.
More information on the dedicated page : https://doc.scalingo.com/platform/app/review-apps#run-a-task-after-the-first-deployment-of-a-review-app
{
"first-deploy": "bundle exec rake db:deploy db:seed"
}
1 nested properties
Job to run as postdeploy hook at the first deployment of a review app or one-click deployed app
If no addons key is specified, the default behaviour is to duplicate the addons from the parent application.
The addons field contains an array of object describing the addons you need to deploy for your review app.
Definitions
If no addons key is specified, the default behaviour is to duplicate the addons from the parent application.
The addons field contains an array of object describing the addons you need to deploy for your review app.
Formation of containers when an app is created
The formation is the definition of the container which will be started once the application is deployed. (Either coming from a one-click deployment button, or a review app from the GitHub integration)
The keys of the environment object are the name of the variables you want to add.
Note: supplying null or an empty string to value will remove the variable from the environment.
It can be used to delete environment variables present in the parent app.
See https://doc.scalingo.com/platform/app/environment