Building BlueGenes for production

The steps details in getting-started are designed to get you up and running for developing BlueGenes. But now that you've completed your snazzy updates and you want to deploy the BlueGenes to production, how do you do it? There are actually a few ways, depending in your needs.

Testing a minified instance before deploying:

Most of the time, we develop with uncompressed files - it's faster for hot reloads. But for production, we want things to be extra fast on load and we don't hot-reload changes, so it's better to present minified files that have had all un-necessary code stripped. Clojure uses Google Closure tools (yup, Clojure uses Closure) to minify things.

Sometimes the Closure compiler is overzealous and removes something we actually wanted to keep. To check what your work looks like in a minified build, run this in the terminal (I'd recommend closing any existing lein run / lein figwheel sessions first).

lein cljsbuild once min + lein run

OR there is also a shortcut - you could just say this for the same results

lein prod

Standalone BlueGenes

One of the easiest ways to deploy the prod minified version is to set up Dokku on your intended server. You can also use BlueGenes with heroku.

Minified deployment using dokku

Once dokku is configured on your remote host, all you need to do to deploy a minified build is add the server as a remote and push to it:

	git remote add my-awesome-server bluegenes@my-awesome-server.git
        git push my-awesome-server master

Uberjar

It's also possible to compile BlueGenes to a jar that will automatically launch a server when executed.

To compile and package BlueGenes into an executable jar, run the following command in the project folder:

$ lein uberjar

Then, to start the application, execute the jar and pass in a config.edn file:

$ java -jar -Dconfig="config/prod/config.edn" target/bluegenes.jar

(When executing the jar the config.edn file can be located anywhere, including your home directory for security.)

BlueGenes as a Jar on Clojars

InterMine 2.0 includes a Gradle target to launch BlueGenes. If you want to update the version of the JAR being launched, you'll need to create an uberjar as abov, OR if it's an official InterMine release, then it can be deployed to clojars, an online artifact repository. Here's how, assuming you have access to deploy to the org.intermine organisation on clojars. Speak to Yo for access if you need it.

Deploying to Clojars

When deploying BlueGenes to Clojars, the JAR file should include all compiled assets include javascript, less, and the vendor libraries. This allows other projects to include BlueGenes as a dependency and deploy the client and server without needing to compile BlueGenes. To deploy a compiled JAR to clojars, include the uberjar profile when running the lein deploy clojars command:

$ lein with-profile +uberjar deploy clojars