From 1cf7851ccb002c95c0ef19a67807fb33895b723b Mon Sep 17 00:00:00 2001
From: Tristan Sloughter
Date: Fri, 26 Jan 2018 17:49:18 -0800
Subject: update create_target.xmlsrc and release structure docs
---
system/doc/system_principles/create_target.xmlsrc | 8 ++++++++
1 file changed, 8 insertions(+)
(limited to 'system/doc/system_principles/create_target.xmlsrc')
diff --git a/system/doc/system_principles/create_target.xmlsrc b/system/doc/system_principles/create_target.xmlsrc
index f9b27ffc35..dc6cbbe980 100644
--- a/system/doc/system_principles/create_target.xmlsrc
+++ b/system/doc/system_principles/create_target.xmlsrc
@@ -263,6 +263,14 @@ os> /usr/local/erl-target/bin/erl -boot /usr/local/erl-target/releases/FI
current directory create not only the file mysystem.rel,
but also file sys.config, the latter file is tacitly
put in the appropriate directory.
+
However, it can also be convenient to replace variables in
+ within a sys.config on the target after unpacking but
+ before running the release. If you have a sys.config.src
+ it will be included and is not required to be a valid Erlang term
+ file like sys.config. Before running the release you must
+ have a valid sys.config in the same directory, so using
+ sys.config.src requires having some tool to populate what is
+ needed and write sys.config to disk before booting the release.