Changeset 1395

Timestamp:

06/06/06 12:27:23 (2 years ago)

Author:

francois

Message:

documented scriptable configuration (ability to put PHP code in YAML files)

Files:

• trunk/doc/book/content/configuration.txt (modified) (2 diffs)

trunk/doc/book/content/configuration.txt

@@ -58 +58 @@
-        # Use blanks instead
-        all:
-��
-����
+  
+    
-
-* To define an array as a value, enclose the elements in square brackets or use the expanded syntax with dashes:
@@ -248 +248 @@
-But maybe you need to add an array, an associative array or a lot of new parameters. In this case it is better to create a new configuration file, together with the corresponding configuration handler.
-
+Scriptable configuration
+------------------------
+
+It may happen that your configuration relies on external parameters (such as a database, or another configuration file). For these particular cases, the symfony configuration files are parsed as a PHP file before being passed to the YAML parser. It means that you can write:
+
+    [php]
+    all:
+      translation:
+        format:  <?php echo sfConfig::get('sf_i18n') == true ? 'xliff' : 'none' ?>
+
+That's right: *you can put PHP code in YAML files*!
+
+Beware though that the configuration is parsed very early in the life of a request, so you will have no symfony built-in methods or functions to help you. If you want one configuration file to rely on another, you have to make sure that the file you rely on is parsed before (look in the [symfony source](http://www.symfony-project.com/trac/browser/trunk/lib/symfony.php) to find in which order the configuration files are parsed). The `app.yml` is one of the last files parsed, so you may rely on others in it. 
+
+Be also aware that in the production environment, the configuration is cached, so the configuration files are parsed (and executed) only once after the cache is cleared.
+
-Configuration handlers
-----------------------