How do deploy Play! on CloudFoundry ...

(prerequisite ruby and gem)
> sudo gem install vmc
> vmc target api.cloudfoundry.com
> vmc login
> cd helloworld (the Play app you created)
> play install cloudfoundry-0.4
> cat conf/dependencies.yml
require:
- play 1.2.4
- play -> cloudfoundry 0.4

> play war --output=../hello --zip
> mv ../hello.war .
> vmc push
Would you like to deploy from the current directory? [Yn]:
Application Name: dmakplayhello
Application Deployed URL [dmakplayhello.cloudfoundry.com]:
Detected a Java Web Application, is this correct? [Yn]:
Memory Reservation (64M, 128M, 256M, 512M, 1G) [512M]:
Creating Application: OK
Would you like to bind any services to 'dmakplayhello'? [yN]:
Uploading Application:
Checking for available resources: OK
Processing resources: OK
Packing application: OK
Uploading (265K): OK
Push Status: OK
Staging Application: OK
Starting Application: OK

> vmc update dmakplayhello (to update your changes to Cloud Foundry)

How do deploy Play! on Jelastic and Heroku ...

http://www.youtube.com/watch?v=SHA5aITE7Ak

HEROKU:
1. create a helloworld app by following http://www.playframework.org/documentation/1.1/firstapp
2. > cd helloworld
3. > git init
4. create .gitignore and add folders to be ignored
5. > git add .
6. > git commit -m init
7. > heroku create -s cedar
8. > git push heroku master
...
-----> Launching... done, v5
http://growing-warrior-4634.herokuapp.com deployed to Heroku

note: if you want to change a new name instead of using growing-warrior-4634, then you can do the following.
1. helloworld> git remote rm heroku
2. helloworld> git remote add heroku git@heroku.com:david-play-hello.git
3. helloworld> git push heroku master
then the new URL will be http://david-play-hello.herokuapp.com
- or -
1. heroku rename david-play-hello --app growing-warrior-4634

JELASTIC:
1. cd helloworld
2. > play war --output=../hello --zip
3. > cd ..
4. > ls hello.war
5. Navigate to jelastic.com and login
6. Upload hello.war and deploy it under Play

IaaS vs PaaS

A major difference between IaaS and PaaS is the amount of control over the system available to users of the services. IaaS provides total control, PaaS typically provides no control. This also means virtually zero administration costs for PaaS whereas IaaS has administration costs similar to a traditional computing infrastructure.

Reference: http://cloud-computing.learningtree.com/2010/08/25/comparing-paas-and-iaas/