X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=doc%2Fbuilding.md;fp=doc%2Fbuilding.md;h=33e1fec3c155b49436e4129817f2285fc4694023;hb=1bf282eb3a5bb347c78d047c7caf12548957749d;hp=badb5933ec99c797f411d6222938d8964252ded4;hpb=663ba999f2b0adfc88121ac131f533c49a305165;p=jalview.git

diff --git a/doc/building.md b/doc/building.md
index badb593..33e1fec 100644
--- a/doc/building.md
+++ b/doc/building.md
@@ -486,6 +486,11 @@ There are several values of `CHANNEL` that can be chosen, with a default of `LOC
     - `appbase` as `http://www.jalview.org/getdown/SCRATCH-NAME/JAVA_VERSION`
     - application subdir as `alt`
     - Getdown launcher cannot use a `file://` scheme appbase.
+* `TEST-LOCAL`:  Like `SCRATCH` but with a specific `test-local` channel name and a local filesystem appbase.  This is meant for testing an over-the-air update on the local filesystem.  An extra property `LOCALDIR` must be given (e.g. `-PLOCALDIR=/home/user/tmp/test`)
+  It will set
+    - `appbase` as `file://${LOCALDIR}`
+    - application subdir as `alt`
+    - Getdown launcher can use a `file://` scheme appbase.
 * `TEST-RELEASE`:  Like `SCRATCH` but with a specific `test-release` channel name.  This won't become live until the actual getdown artefact is synced to the web server.  This is meant for testing an over-the-air update without interfering with the live `release` or `develop` channels.
   It will set
     - `appbase` as `http://www.jalview.org/getdown/test-release/JAVA_VERSION`