Added a Dockerfile.

Dockerfile

@@ -0,0 +1,15 @@
+FROM clojure:alpine
+VOLUME /data
+LABEL description="code-maat docker image."
+
+ARG dest=/usr/src/code-maat
+
+RUN mkdir -p $dest
+WORKDIR $dest
+COPY project.clj $dest
+RUN lein deps
+COPY . $dest
+RUN mv "$(lein uberjar | sed -n 's/^Created \(.*standalone\.jar\)/\1/p')" app-standalone.jar
+
+ENTRYPOINT ["java", "-jar", "app-standalone.jar"]
+CMD []

README.md

@@ -37,6 +37,10 @@ Add the following line to your leiningen dependencies in case you want to use Co
 
 	   [code-maat "1.0.1"]
 
+You can also build code-maat as a Docker image:
+
+      docker build -t code-maat-app .
+
 Code Maat operates on log files from version-control systems. The supported version-control systems are `git`, Mercurial (`hg`), `svn`, Perforce (`p4`), and Team Foundation Server (`tfs`). The log files are generated by using the version-control systems themselves as described in the following sections.
 
 ### Generating input data
@@ -87,6 +91,12 @@ If you've built a standalone jar (`lein uberjar`), run it with a simple java inv
 
      	  java -jar code-maat-0.8.6.jar -l logfile.log -c <vcs>
 
+If you've built a docker container, then you can run it as
+
+        docker run -v /home/xx/src/code-maat:/data -it code-maat-app -l /data/logfile.log -c <vcs>
+
+where the /home/xx/src/code-maat is the host's directory containing the file logfile.log.
+
 When invoked with `-h`, Code Maat prints its usage:
 
              adam$ java -jar code-maat-0.9.0.jar