Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Example Play Slick Project

Subscribe to updates I use play-isolated-slick

Statistics on play-isolated-slick

Number of watchers on Github 139
Number of open issues 0
Average time to close an issue 3 months
Main language Scala
Average time to merge a PR 1 day
Open pull requests 1+
Closed pull requests 12+
Last commit almost 2 years ago
Repo Created over 4 years ago
Repo Last Updated over 1 year ago
Size 81 KB
Organization / Authorplayframework
Page Updated
Do you use play-isolated-slick? Leave a review!
View play-isolated-slick activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating play-isolated-slick for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

Play with Slick 3.1

Build Status

This project shows Play working with Slick.

This project is configured to keep all the modules self-contained.

  • Slick is isolated from Play, not using play-slick.
  • Database migration is done using Flyway, not Play Evolutions.
  • Slick's classes are auto-generated following database migration.

Database Migration

sbt flyway/flywayMigrate

Slick Code Generation

You will need to run the flywayMigrate task first, and then you will be able to generate tables using sbt-codegen.

sbt slickCodegen


You can run functional tests against an in memory database and Slick easily with Play from a clean slate:

sbt clean flyway/flywayMigrate slickCodegen compile test


To run the project, start up Play:

sbt run

And that's it!

Now go to http://localhost:9000, and you will see the list of users in the database.

play-isolated-slick open pull requests (View All Pulls)
  • Upgrade branch master using TemplateControl
play-isolated-slick list of languages used
Other projects in Scala