Add Travis CI publish on tag

Author: benhylau

.travis.yml

@@ -0,0 +1,17 @@
+install: "./install-dependencies.sh"
+
+script: "./build.sh"
+
+before_deploy: "./package $TRAVIS_TAG"
+
+deploy:
+  provider: releases
+  api_key:
+    secure: VnXRjvEsJKZJ0mto3ZMOFccE8QzuRvqyxm6juM05g3Z9GuC1E3wuQI+3N0qSinkxUpzbjfSWhBSeApN7cKPKYJTBehDA6euQyTTY12LbZliSNkwmS2YBfPjJqll4/kCLMzYvaQwVbPijhIUYOCUI/6x28OGJUSohdH3RplJ68LGsIzbTkZ/j17u6iKDIqzmazngTMriWaNC5eKGTSYLXbTibJxJtYOTi8OcsvuAd5KGQpU06MJFxB5ARCK1WATwHIeLWsIKux670vJkH2duYRxexirRcL5C42PwqqihalW4JC7nEilC2IMq2MUGlTeO2ph8UEKZ4O/w0BZTOvb1SJ2YJlfF1lm1Hu/LiEw1pDzkWA1DcneyvAezCjJ9cEjqT2nRPqBY3e/OSjpH7pFMr0o8xaX0N3MRzvZ7Lu/7Ds/DMZeavqE+UVLLvb3BKqboJYwl3T0tN452zUkGpiP+MNW+ZECKbd5FGF9kpSLfGG4rT7FFtVAvPkqzwKuX+1QCFOXemrrtfcL6H7uDIJzlzz7qxccIo5rGfeb/XXNeAVc0+L3S9DNHN+L6u0T5kOMiwO6sLabjBrqhiA6yowSMlSV1oKWDeXkzYZBC+05bA/cRpC6W+49+I1zBze9qe4YMZ1ztDtlV/E5LfbfisrWSjQQRhyvA7FxVsXLw/Q5st17Q=
+  file:
+    - "publish/workshop-materials-$TRAVIS_TAG.tar.gz"
+    - "publish/workshop-materials-$TRAVIS_TAG.zip"
+  skip_cleanup: true
+  on:
+    repo: tomeshnet/p2p-internet-workshop
+    tags: true

README.md

@@ -55,7 +55,7 @@ Participants will be expected to bring their own laptop.
 
 Workshop materials such as lesson plans and worksheets are written as simple [Markdown](https://en.wikipedia.org/wiki/Markdown) files. Each presentation slide deck is created as a Markdown-based [GitBook](https://www.gitbook.com). All generated assets are published to [GitHub Pages individually](https://github.com/tomeshnet/p2p-internet-workshop/tree/gh-pages) and [GitHub Releases as an archive](https://github.com/tomeshnet/p2p-internet-workshop/releases) for download.
 
-If you want to generate these assets yourself, simply run `./build` and you will find the generated assets in the `output` folder. The `./release` script is used to zip up the generated assets into archives convenient for download, which is the form you will find in the GitHub Releases.
+If you want to generate these assets yourself, simply run `./install-dependencies.sh` and `./build.sh` and you will find the generated assets in the `output` folder. The `./package.sh` script is used to zip up the generated assets into archives convenient for download, which is the form you will find in the GitHub Releases.
 
 When using the GitBook presentations at a workshop, you can either:
 

build renamed to build.sh

@@ -1,24 +1,5 @@
 #!/usr/bin/env bash
 
-# Check for required tools
-echo "Checking for markdown-pdf node module"
-npm -g list markdown-pdf
-S=$?
-if [ $S -ne 0 ]; then
-    echo "markdown-pdf is missing, install by running:"
-    echo "    npm install -g markdown-pdf"
-    return $S
-fi
-
-echo "Checking for gitbook-cli node module"
-npm -g list gitbook-cli
-S=$?
-if [ $S -ne 0 ]; then
-    echo "gitbook-cli is missing, install by running:"
-    echo "    npm install -g gitbook-cli"
-    return $S
-fi
-
 # Delete generated assets
 rm -rf output
 mkdir output

install-dependencies.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+
+# Check for required tools
+echo "Checking for markdown-pdf node module"
+npm -g list markdown-pdf
+S=$?
+if [ $S -ne 0 ]; then
+    echo "markdown-pdf is missing, install by running:"
+    echo "    npm install -g markdown-pdf"
+    return $S
+fi
+
+echo "Checking for gitbook-cli node module"
+npm -g list gitbook-cli
+S=$?
+if [ $S -ne 0 ]; then
+    echo "gitbook-cli is missing, install by running:"
+    echo "    npm install -g gitbook-cli"
+    return $S
+fi

release renamed to package.sh

@@ -1,16 +1,11 @@
 #!/usr/bin/env bash
-#
-# Package assets for release
-#
 
-RELEASE_VERSION=0.2
-
-./build
+RELEASE_VERSION=$1
 
 # Create directory for release assets ready to be published
 rm -rf publish
 mkdir publish
 
 # Package assets in tar.gz and zip formats
 tar --create --gzip -f "publish/workshop-materials-${RELEASE_VERSION}.tar.gz" -C output .
-cd output; zip --recurse-paths "../publish/workshop-materials-${RELEASE_VERSION}.zip" .; cd ..
+cd output; zip --recurse-paths "../publish/workshop-materials-${RELEASE_VERSION}.zip" .; cd ..