[Catalyst-commits] r7299 - trunk/examples/CatalystAdvent/root/2007/pen

jshirley at dev.catalyst.perl.org jshirley at dev.catalyst.perl.org
Fri Dec 14 18:46:30 GMT 2007


Author: jshirley
Date: 2007-12-14 18:46:30 +0000 (Fri, 14 Dec 2007)
New Revision: 7299

Modified:
   trunk/examples/CatalystAdvent/root/2007/pen/CatalystConfig.pod
Log:
Fixing up merge doc to be more accurate

Modified: trunk/examples/CatalystAdvent/root/2007/pen/CatalystConfig.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2007/pen/CatalystConfig.pod	2007-12-14 18:27:44 UTC (rev 7298)
+++ trunk/examples/CatalystAdvent/root/2007/pen/CatalystConfig.pod	2007-12-14 18:46:30 UTC (rev 7299)
@@ -83,14 +83,24 @@
 =head2 ConfigLoader: The Aptly Named Configuration Loader
 
 The great thing that L<Catalyst::Plugin::ConfigLoader> does for you is merging
-the various configurations.  Rather than simply overwrite the entirety of
-a components configuration, it will merge them giving precedence up the chain
-towards "human editability".
+the various external configurations.  Rather than simply overwrite the entirety
+of a components configuration, it will merge external files and give them
+precedence.  The higher the "human editability" of the configuration, the
+higher the precedence.
 
-The lowest is the component package (ConfigEg/Model/Foo.pm), up next is
-ConfigEg.pm and the last step is the individual configuration files.  By default
-this would be configeg.yml and the final word is configeg_local.yml
+=head2 Configuration Merging
 
+Catalyst will automatically merge all the various sections of configuration into
+one easy to use structure.  ConfigLoader handles taking the external files, and
+Catalyst will take that information and merge it with the internal configuration
+of the components.
+
+To illustrate this, here is a brief example.  The lowest in configuration
+precedence is the component package itself (C<ConfigEg/Model/Foo.pm>), up next
+is C<ConfigEg.pm> and the highest is the individual configuration files loaded
+by ConfigLoader, which pulls in the external files.  By default this would be
+configeg.yml and configeg_local.yml.
+
 By merging, what happens is if you have the following (completely and totally
 fabricated) structure in the component package C<ConfigEg/Model/Foo.pm>:
 




More information about the Catalyst-commits mailing list