Play2 @CloudBees

Play2 @CloudBees

CloudBees & Play2 Java?

CloudBees gives you kickstart, if you are a Scala fellow. They build you app with everything included, deploy it, and you just need to get it down to your own sandbox to develop it further. 

For Play2 Java they don't offer same option. Java can be taken in use without problems, anyway, since you just need to add needed dependencies for libraries you use and start coding.

http://www.playframework.com/documentation/2.2.x/Deploying-to-CloudBees

Recipe

Register free account 

• https://www.cloudbees.com/signup

Create Play2 app at Clickstart

• https://grandcentral.cloudbees.com/?#doClickStart
• Give name of app, ex. play2-cloudbees

Test your app

• http://play2-cloudbees.<account-name>.cloudbees.net

Find url to repository

• https://forge.cloudbees.com
• select your app
• see address of Authenticated access (https)

Clone app

• git clone https://git.cloudbees.com/<account-name>/play2-cloudbees.git 

Make changes

Edit templates

• any file goes, but on scala html templates you see changes right away
• example, file: app/views/index.scala.html, change text: "What's your name"

Push changes

• git add -A
• git commit -m 'change'
• git push origin master

Test your app again

• http://play2-cloudbees.<account-name>.cloudbees.net

Further steps

CloudBees goes on Play2 in full Scala mode - also: example app created by ClickStart doesn't have Java option. Fine for many, but I wanted still to work with Java, and so do many of us - old legacy java coders don't convert to Scala overnight, and neither do managers.

I felt CloudBees bit confusing. There's couple of deploying options for changes, couple of ways developing your initial seed app, and it was not cleat to me what is preferred way. I tried plugins and git deployments, and managed to push post my changes to git and deploy new version of app  to CloudBees, but I didn't feel it intuitive to control deployments.