When deploying a Play!2 app on cloudfoundry I would like to be able to specify at least one additional parameter to the startup command.
Currently it seems like cloudfoundry uses the start script created by Play2 without any arguments, but to override the default application configuration with specific production values I need it to be called with -Dconfig.resource=prod.conf
I couldn’t find any way to do this, maybe through the manifest.yml but I wasn’t able to find a specification for how to add this param.
Appart from this I was able to successfully deploy play 2.0 and play 2.1 apps to cloudfoundry
Reading the source code for the cloudfoundry tooling I found out that the vcap-staging plugin for play does not honor the “command” attribute in manifest.ml nor does it ask for one. It automatically assume that the application will be started with the “start” (see line 10 in plugin.rb).
However, it does honor the JAVA_OPTS environment variable.
In the end, I was able to do
And get it working as I wanted.