Written by Eric Normand. Published: December 15, 2012
Sign up for weekly Clojure tips, software design, and a Clojure coding challenge.
Continuous integration
Clojure Gazette
Issue 1.27 - December 15, 2012
editorial
Clojure integration
I have been automating some of my deployments for various projects I work on, and I thought I would share a few of the tools I have been using. Once you automate, you will have more free time to read and watch the rest of the posts.
Jenkins is a continuous integration server. It builds, tests, and deploys based on triggers. I like Jenkins because of its easy setup and many plugins. Be sure to install the leiningen and git plugins.
This talk is an introduction to Pallet focusing on key aspects where it differs from the current mainstream DevOps tooling. It will cover some of the abstractions in Pallet that make it distinct from Puppet or Chef, and we will illustrate this with some real world use cases for these.
Douglas Crockford tries his hand at the ubiquitous monad tutorial by developing a couple in Javascript. He does a good job explaining how we already use monads even if we didn't know it.
lein-dalap allows you to author code that works in both the JVM and in the browser, without forking your code and without relying on cljsbuild crossovers.
James Reeves talks about alternatives to MVC, how to modularize your resources, and how to then relate them back together. He starts from a typical Rails-style MVC app and organizes it in a way that works best with Clojure.
I have not used this, but I think I will soon. It is a system similar to socket.io but for the JVM. It abstracts away different browser/server communication methods to allow efficient message passing between a web browser and a JVM web server. The documentation is extensive and professional.