From 286ff02ff02b9502aa07c3d0a1f6f17dbd2af61a Mon Sep 17 00:00:00 2001
From: Leigh McCulloch <leigh@mcchouse.com>
Date: Mon, 1 Aug 2016 22:32:15 -0700
Subject: [PATCH] Improved README's usage for custom volumes.

What
===
Added `-v` and `volumes` to the usage.

Why
===
So it's clear that they need to be provided when defining custom volume locations instead of the default `/unison`. The Dockerfile contains a `VOLUME` command which is set to `/unison` when building, which is why the `volumes` definition in the docker-compose file and the `-v` on the command line are unnecessary when it is unchanged.
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 56b3706..daf666a 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ The docker image is available on Docker Hub:
 First, you can launch a volume container exposing a volume with Unison.
 
 ```bash
-$ CID=$(docker run -d -p 5000:5000 -e UNISON_WORKING_DIR=/unison leighmcculloch/unison:latest)
+$ CID=$(docker run -d -p 5000:5000 -e UNISON_WORKING_DIR=/unison -v /unison leighmcculloch/unison:latest)
 ```
 
 You can then sync a local folder to `/unison` in the container with:
@@ -41,6 +41,8 @@ unison:
   image: leighmcculloch/unison:latest  
   environment:  
     - UNISON_WORKING_DIR=/unison  
+  volumes:
+    - /unison
   ports:  
     - "5000:5000"
 ```