Added value substitution

2 files changed, 104 insertions, 51 deletions

diff --git a/CONFIGURE.md b/CONFIGURE.md
index 0da7842..409d962 100644
--- a/CONFIGURE.md
+++ b/CONFIGURE.md
@@ -82,6 +82,60 @@ the lager logging system, only the ```rvi``` tuple needs to be edited.
 
 The term tuple and entry will be intermixed throughout this document.
 
+## CONFIGURATION FILE VALUE SUBSITUTION
+All string values under the rvi tuple tree are scanned
+for specific dokens during startup. If a token is 
+found, it will be replaced with a value referenced by it.
+Tokens can one of the following:
+
+* ```$rvi_file(FileName,Default)``` - File content<br>
+  When an ```$rvi_file()``` token is encountered, the first line of
+  the referenced file is read. The line (without the newline)
+  replaces the token.<br>
+  Example:<br>
+  ```{ node_service_prefix, "jlr.com/vin/$rvi_file(/etc/vin,default_vin)"}```
+
+  will be substituted with the first line from the
+  file ```/etc/vin```:
+
+  ```{ node_service_prefix, "jlr.com/vin/2GKEG25HXP4093669"}```
+  
+  If ```/etc/vin``` cannot be opened, the value ```default_vin```
+  will be used instead.
+
+* ```$rvi_env(EnvironemtnName,Default)``` - Environment variable<br>
+  When an ```$rvi_env()``` token is encountered, the value of 
+  the Linux process environment variable (such as $HOME) is read
+  to replace the token.<br>
+
+  Example:<br>
+    ```{ node_service_prefix, "jlr.com/vin/$rvi_env(VIN,default_vin)"}```
+
+    will be substituted with the value of the ```$VIN``` environment
+    variable:
+
+
+    ```{ node_service_prefix, "jlr.com/vin/2GKEG25HXP4093669"}```
+  
+    If VIN is not a defined environment variable, the value
+    ```default_vin``` will be used instead.
+
+* ```$rvi_uuid(Default)``` - Unique machine identifier<br>
+  When an ```$rvi_uuid()``` token is encountered, the UUID of the root
+  disk used by the system is read to replace the token.
+  The UUID of the root disk is retrieved by opening ```/proc/cmdline```
+  and extracting the ```root=UUID=[DiskUUID]``` value.
+  This value is generated at system install time and is reasonably
+  world wide unique.
+
+  Example:<br>
+    ```{ node_service_prefix, "jlr.com/vin/$uuid(default_vin)"}```
+
+  will be substituted with the value of the root disk UUID:
+    ```{ node_service_prefix, "jlr.com/vin/afc0a6d8-0264-4f8a-bb3e-51ff8655b51c"} ```
+  
+  If the root UUID cannot be retrieved, the value ```default_vin```
+  will be used instead.
 
 # SPECIFY NODE SERVICE PREFIX #
 All RVI nodes hosting locally connected services will announce these
@@ -650,7 +704,8 @@ Replace debug with info, notice, warning, or error for different log
 levels. A production release will also produce logs to
 ```rel/[release]/log/erlang.log.?```.
 
-Check the file modification date to find which of the log files are currently written to.
+Check the file modification date to find which of the log files are
+currently written to.
 
 You can configure the log level through the lager configuration entry:
 
@@ -667,6 +722,6 @@ You can configure the log level through the lager configuration entry:
 
 Additional handlers can also be added for different log destinations. 
 
-See Basho's lager documentation at [github](https://github.com/basho/lager) for details
-on logging.
+See Basho's lager documentation at
+[github](https://github.com/basho/lager) for details on logging.
 
diff --git a/RELEASE.md b/RELEASE.md
index 5f28d3c..e1a7386 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -1,10 +1,48 @@
 # RELEASE NOTES #
 
-# v0.1 #
-Initial demo version. Works with the hvac_demo and its hvac / mobile emulators.
 
-# v0.2 #
-Various improvements
+# v0.4.0 #
+
+* <b>Rewrite to better handle multiple components</b><br>
+  Multiple data links and protocols can now be handled
+
+* <b>Replace static rules with routes</b><br>
+  We can now route messages depending on their targeted service names.
+  Each route specify a protocol and data link to use, together with
+  options indicating how that route should be managed.
+
+* <b>Bluetooth</b><br>
+  Using dlink_bt, two RVI nodes can now communicate over an RFCOMM link.
+
+
+# v0.3.2 #
+* <b>Re-enable service availability notifications over websockets</b><br>
+  Issue 15 was an artifact of issue 14, thus we can turn notifications back on
+  now that 15 is fixed.
+
+* <b>Implement datalinkbert_rpc pings</b><br>
+  This fixes issue #14 where a rebooted tizen box did not shut down
+  the data link tcp connection correctly, which left it dangling on
+  the server. A periodic tcp (5 min default) will trigger a
+  kernel-originated shutdown when the remote address cannot be
+  reached.
+
+* <b>Filter out resurrected services when a remote data link disappears</b><br>
+  This fixes issue #14 where a rebooted tizen box would register its
+  services while its old (pre-reboot) dangling tcp connection was
+  still alive from the server's point of view. When the danlging tcp
+  connection died, the RVI would delete all services associated with
+  it, thus deleting active services registered over the new connection
+  after the tizen box rebooted.
+
+  We now filter any services associated with a dead tcp connection
+  against identically named services registered over other
+  connections.
+
+# v0.3.1 #
+
+* <b>Don't send service availablity notifications over websockets</b><br>
+  For unknown reasons this crashes the RVI node intermittently
 
 # v0.3.0 #
 * <b>Auto connect static links</b><br>
@@ -51,50 +89,10 @@ Big data demo moved to its own repo at https://github.com/PDXostc/rvi_bigdata
 * <b>SOTA demo moved</b><br>
   SOTA demo moved to its own repo at https://github.com/PDXostc/rvi_sota_demo
 
-# v0.3.1 #
-
-* <b>Don't send service availablity notifications over websockets</b><br>
-  For unknown reasons this crashes the RVI node intermittently
-
-# v0.3.2 #
-* <b>Re-enable service availability notifications over websockets</b><br>
-  Issue 15 was an artifact of issue 14, thus we can turn notifications back on
-  now that 15 is fixed.
-
-* <b>Implement datalinkbert_rpc pings</b><br>
-  This fixes issue #14 where a rebooted tizen box did not shut down
-  the data link tcp connection correctly, which left it dangling on
-  the server. A periodic tcp (5 min default) will trigger a
-  kernel-originated shutdown when the remote address cannot be
-  reached.
-
-* <b>Filter out resurrected services when a remote data link disappears</b><br>
-  This fixes issue #14 where a rebooted tizen box would register its
-  services while its old (pre-reboot) dangling tcp connection was
-  still alive from the server's point of view. When the danlging tcp
-  connection died, the RVI would delete all services associated with
-  it, thus deleting active services registered over the new connection
-  after the tizen box rebooted.
-
-  We now filter any services associated with a dead tcp connection
-  against identically named services registered over other
-  connections.
-
-# v0.4.0 #
-
-* <b>Certificate / Signature management</b><br>
-  First implementation of RVI authentication, authorization, and
-  authorization-filtered service discovery.
-
-* <b>Rewrite to better handle multiple components</b><br>
-  Multiple data links and protocols can now be handled
-
-* <b>Replace static rules with routes</b><br>
-  We can now route messages depending on their targeted service names.
-  Each route specify a protocol and data link to use, together with
-  options indicating how that route should be managed.
+# v0.2 #
+Various improvements
 
-* <b>Bluetooth</b><br>
-  Using dlink_bt, two RVI nodes can now communicate over an RFCOMM link.
+# v0.1 #
+Initial demo version. Works with the hvac_demo and its hvac / mobile emulators.