Merge pull request #4 from it33/master

Updating to Mattermost v1.4.0

README.md

@@ -6,10 +6,12 @@
 
 1. Don't make configuration changes in the Mattermost admin console.
    Any configuration changes in the Mattermost admin console will likely be lost on dyno restart (which may be every 24 hours) and will likely not be distributed across multiple dynos.
-2. Not using s3 means any uploads will be lost on dyno restart or application reconfiguration or redeploy and won't be consistent across multiple dynos.
-   Without s3 backing this is not anything more than a one time demo.
+2. Not using S3 means any uploads will be lost on dyno restart or application reconfiguration or redeploy and won't be consistent across multiple dynos.
+   Without S3 backing this is not anything more than a one-time demo.
 
 ## ToDo
 
-1. Configurable versions (currently hard-coded to v1.2.1)
+1. Configurable versions (currently hard-coded to v1.4.0)
 2. More configurable options
+
+To use a different version of Mattermost update the version specified in `bin/compile`

bin/compile

@@ -6,6 +6,6 @@ BUILD_DIR=$1
 CACHE_DIR=$2
 ENV_DIR=$3
 
-echo "-----> Retrieving mattermost v1.2.1 tar"
-curl -s -L https://github.com/mattermost/platform/releases/download/v1.2.1/mattermost.tar.gz | tar -zxf - --strip-components=1 -C ${BUILD_DIR}
+echo "-----> Retrieving mattermost v1.4.0 tar"
+curl -s -L https://github.com/mattermost/platform/releases/download/v1.4.0/mattermost.tar.gz | tar -zxf - --strip-components=1 -C ${BUILD_DIR}
 mkdir data/