Our aim for Scalingo is to be fully compatible with Heroku. If your app works on Heroku, it will work on Scalingo. We have added several compatibility layers for that matter.
If a Procfile is available in the source code of your app, it will be used. See the dedicated Procfile page for more information.
release entry does not exist on Scalingo, and thus it won’t be executed.
The postdeploy hook
exists with similar functionality.
The difference is that the
postdeploy hook is only getting executed at the
end of a successful deployment, not at each change of variable/addon
modification (creating a release).
Most buildpacks and their functionalities work exactly the same as on Heroku. Some buildpacks are written and maintained on our own.
It’s open source. Check our GitHub account to see the whole list.
Heroku uses the file
app.json for describing your application.
The file on Scalingo is named
scalingo.json and its format is fully
compatible with the format used by Heroku.
The Scalingo manifest file has a few specifics. You can find out more about it in the dedicated documentation page: Scalingo JSON Manifest.
Based on a Git hook. Just git push your code!