Scala is officially supported on Scalingo.
It uses sbt 0.11.0+.
$ ls Procfile build.sbt project src $ scalingo create my-app $ git push scalingo master ... -----> Scala app detected -----> Building app with sbt -----> Running: sbt compile stage
The buildpack will detect your app as Scala if it has the
project/build.properties and either
*.sbt in the root directory or
.sbt/*.scala. It vendors a version of sbt and your
.ivy/cache into your container. The
.ivy2 directory will be
cached between builds to allow for faster build times.
In some cases, builds need to clean artifacts before compiling. If a clean
build is necessary, configure builds to perform clean by setting
$ scalingo env-set SBT_CLEAN=true SBT_CLEAN has been set to true.
All subsequent deploys will use the clean task. To remove the clean task, unset
$ scalingo env-unset SBT_CLEAN SBT_CLEAN has been unset.
Not a Valid Command: stage
[error] Not a valid command: stage [error] Not a valid project ID: stage [error] Expected ':' (if selecting a configuration) [error] Not a valid key: stage [error] stage [error] ^
In this situation, your project lacks the package
sbt-native-packager. This plugin
aims at packaging Scala applications into various kind of destination packages.
You need to add the depdencendy in your
addSbtPlugin("com.typesafe.sbt" % "sbt-native-packager" % "1.3.18")
Then once done, enable the packaging into a Java app for your project (in your
That’s it, the
stage command will now be found by our deployment system.
More information at https://github.com/Scalingo/scala-buildpack.