https://github.com/mariussoutier/play-multi-multi-project

Example of building Playframework applications that consist of multiple services and multiple sub-modules
https://github.com/mariussoutier/play-multi-multi-project

playframework scala

Last synced: about 3 hours ago
JSON representation

Example of building Playframework applications that consist of multiple services and multiple sub-modules

• Host: GitHub
• URL: https://github.com/mariussoutier/play-multi-multi-project
• Owner: mariussoutier
• License: other
• Created: 2014-10-11T19:52:16.000Z (about 10 years ago)
• Default Branch: master
• Last Pushed: 2017-02-03T14:31:42.000Z (almost 8 years ago)
• Last Synced: 2024-04-16T10:21:20.020Z (7 months ago)
• Topics: playframework, scala
• Language: Scala
• Homepage:
• Size: 43 KB
• Stars: 44
• Watchers: 5
• Forks: 10
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Play Multi-Project

An example of building applications that consist of multiple services.

First off, the top-level project is an sbt multi-project. It defines two Play applications, `app1` and `app2`. It also

defines a non-Play project `model` that contains code shared by the Play applications.

Each Play app is then split into a master app, and Play sub-modules (in this case only an admin module). Play sub-modules

follow Play conventions, but require to use a separate routes file and sub-package for controllers and views. They

cannot have conf files.

Note how sbt plugins are only defined by the root build.

## Running

You can run each app individually by using `sbt ";project app;run`. Two scripts are provided for this.

## Testing

`sbt test` will run all tests in all sub-projects.