Signup for CloudBees to create an account.
Download the CloudBees SDK and install. (See later for the case where the CloudBees SDK is not installed.)
Verify that you can execute bees app:list. The first time a bees command is executed it will prompt for your user name and password so that your API key and API secret can be downloaded and cached in the ~/.bees/bees.config properties file. This key and secret will be used to authenticate when using the CloudBees SDK or the lein CloudBees plugin.
Modify the project.clj file to identify the application:
:cloudbees-app-id "<account>/<appname>"
Where account is the name of your account and appname is the name of your application.
Modify the project.clj file to include the following development dependency:
Modify the project.clj file to include the following development dependency:
[lein-cloudbees "1.0.1"]
for example:
(defproject mandel"1.0.0-SNAPSHOT"
:description "A Mandelbrot web app"
:cloudbees-app-id "sandoz/mandel"
:dependencies [[org.clojure/clojure "1.3.0"]
[org.clojure/clojure-contrib "1.2.0"]
[compojure "0.6.4"]]
:dev-dependencies [[lein-ring "0.4.6"]
[lein-cloudbees "1.0.1"]]
:ring {:handler mandel.core/app})
Verify that lein cloudbees works, you should see something like the following:
Deploy the application:
$ lein cloudbees
Manage a ring-based application on Cloudbees.
Subtasks available:
list-apps List the current applications deployed to CloudBees.
deploy Deploy the ring application to CloudBees.
tail Tail the runtime log of the deployed application.
restart Restart the deployed application.
stop Stop the deployed application.
start Start the deployed application.
Arguments: ([list-apps deploy tail restart stop start])
Deploy the application:
$ lein cloudbees deploy
Created /Users/sandoz/Projects/clojure/mandel/.project.zip
Deploying app to CloudBees, please wait....
http://mandel.sandoz.cloudbees.net
Applcation deployed.
The deployment creates an uber war and then deploys that war to CloudBees. The deployment process is smart, only changes will be sent and furthermore any jars in WEB-INF/lib will be checked, securely, against a global cache, before sending. So even if the uber war is rather big the actual stuff sent across the wire may be much less than expected, even on the first deployment.
Eh Voila! your application is deployed and the state can be verified:
$ lein cloudbees list-apps
sandoz/mandel - active
If you don't have the CloudBees SDK installed then you can reference the API key and secret key in the project.clj, for example:
:cloudbees-api-key ~(.trim (slurp "/Users/sandoz/cloudbees/sandoz.apikey"))
:cloudbees-api-secret ~(.trim (slurp "/Users/sandoz/cloudbees/sandoz.secret"))
Such declarations will take precedence over any API key and secret key declared in the ~/.bees/bees.config properties file.
It's a bad idea to reference the key and secret directly in the project.clj and instead it is better to refer to that information in a file. Slurp them in from a file to a string, then trim to remove any white space or line-feeds (the plugin needs to be modified to trim those values).
