Deploying Play Framework 2 apps, with Java AND Scala, to Openshift
Join the DZone community and get the full member experience.Join For Free
Let's Play! in the cloud
A couple of weeks ago, Mark Atwood, Jorge Aliss, and I, Sebastián Scarano participated in Red Hat's webinar LET'S PLAY! IN THE CLOUD: DEVELOPING JAVA WEB APPS ON OPENSHIFT
In the webinar Mark gave a neat introduction to Openshift, Red Hat's free Platform as a Service (click on the image to see video):
Then we developed a basic contact manager web application, combining Java and Scala source code in the same Play 2 application, and deployed it on Openshift (click on the image to see video).
With this quickstart (https://github.com/opensas/play2-openshift-quickstart) you'll be able to take any Play 2 application and deploy it on openshift. Just follow this instructions.
And here (https://github.com/opensas/play2-contacts-demo) you will find the contact demo app.
In the demo, in spite our internet connection conspiring against us, we managed to cover the following topics:
- Creating a new play 2 application
- Basic application structure
- Configuring your IDE to work with a Play application
- Persisting your data to an in-memory database with Ebean
- Adding Validations
- Working with Scala Templates
- Mixing Java and Scala source code in the same application
- Integrating twitter bootstrap
- Customizing your app cofiguration for running on Openshift
- Persisting your data to a file database when running on Openshift
- And finally, deploying your application on Openshift
You can also check this article in which we explain in detail how we took advantage of the new "do-it-yourself" application type on Openshift to achieve native support for Play Framework application on Openshift. So, if you want to start deploying your play apps on openshift right away, just sign up at openshift.com and enter PLAY!WEBINAR as promotional code, and you'll get 3 gears, each with 1GB ram and 512 MB data space, for free.
Have fun playing on the cloud!
Opinions expressed by DZone contributors are their own.