Docker image with sbt and dependencies needed to launch Play 2.5.18 applications.

Includes:

• OS: Alpine 3.4
• Java: Oracle Java 8
• Sbt version: 0.13.15
• Git
• Node.js
• Play Framework: 2.5.18 (with scala 2.11.11, jpa, hibernate 5.2.5 , mockito 2.1.0, sbt web plugins)
• Based on image: anapsix/alpine-java:8_jdk

The image contains the ivy2 and sbt dependencies for Play Framework 2.5.18. They are located in /root/.ivy2 and /root/.sbt directories.

This image is not meant to be used for another version of Play. If you try to compile or run a Play project configured for another version it will donwload all the new dependencies in the container. This takes a lot of time and is useless, because the next time the container is created, all the dependencies have disapeared and the process has to begin again.

You can look and change the play version of a project in the project/plugins.sbt file.

Exports a volume on /code in which you have to mount the Play 2.5.18 project directory.

The CMD in the Dockerfile launch the sbt command. The docker run command launches the sbt console in the container, where you can enter any sbt command: compile, run, test, clean, etc.

For instance, to run a play project in the /path/to/my/play/project directory:

$ cd /path/to/my/play/project
$ docker run --rm  -it -v "${PWD}:/code" -p 9000:9000 domingogallardo/playframework
[play-project] $ test
...
[success] Total time: 21 s, completed Jun 30, 2017 7:33:27 AM
[play-project] $ run
(you can test your play app on localhost in your host machine)
(use Enter to stop and go back to the console)
[play-project] $ exit

The exported port 9000 is the default play port.

You can also launch an explicit sbt command when launching the container.

For instance, to execute the tests:

docker run --rm -v "${PWD}:/code" domingogallardo/playframework sbt test

Or to run the application:

docker run --rm -it -v "${PWD}:/code" -p 9000:9000 domingogallardo/playframework sbt run