Make config variables a lot more useful.

- Config variables now no longer conflict with regular values.

- Config variables can now be read from the environment.
  (e.g. ${env.USER}).

- Config variables can now be used as partial values
  (e.g. support@${network.domain})

1 files changed, 9 insertions, 6 deletions

diff --git a/data/stats.standalone.example.conf b/data/stats.standalone.example.conf
index 27af0e182..a85099529 100644
--- a/data/stats.standalone.example.conf
+++ b/data/stats.standalone.example.conf
@@ -79,17 +79,20 @@
 /*
  * [OPTIONAL] Defines
  *
- * You can define values to other values, which can be used to easily change
- * many values in the configuration at once.
+ * You can use defines for repeated information, which can be used to easily change many
+ * values in the configuration at once.
+ *
+ * To use a define called foo.bar you use ${foo.bar} in your config file. You can also use
+ * environment variables by prefixing their name with "env." like ${env.USER}.
  */
 
 /*
- * The stats.host define is used in multiple different locations throughout the
- * configuration for the stats client hostname.
+ * The services.host define is used in multiple different locations throughout the
+ * configuration for the server name and pseudoclient hostnames.
  */
 define
 {
-	name = "stats.host"
+	name = "services.host"
 	value = "stats.example.com"
 }
 
@@ -208,7 +211,7 @@ serverinfo
 	 * other server names on the rest of your IRC network. Note that it does not have
 	 * to be an existing hostname, just one that isn't on your network already.
 	 */
-	name = "stats.example.com"
+	name = "${services.host}"
 
 	/*
 	 * The text which should appear as the server's information in /WHOIS and similar