|
|
@@ -1,5 +1,5 @@
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
-<!-- EN-Revision: 17171 -->
|
|
|
+<!-- EN-Revision: 21357 -->
|
|
|
<!-- Reviewed: no -->
|
|
|
<sect2 id="zend.application.core-functionality.application">
|
|
|
<title>Zend_Application</title>
|
|
|
@@ -142,7 +142,7 @@
|
|
|
<listitem>
|
|
|
<para>
|
|
|
<varname>$options</varname>
|
|
|
- >:
|
|
|
+ :
|
|
|
<emphasis>opcional</emphasis>
|
|
|
.
|
|
|
El argumento puede ser uno de los siguientes valores:
|
|
|
@@ -161,6 +161,21 @@
|
|
|
determinar qué sección de la configuración
|
|
|
se traerá.
|
|
|
</para>
|
|
|
+ <para>
|
|
|
+ As of 1.10, you may also pass multiple paths containing
|
|
|
+ config files to be merged into a single configuration.
|
|
|
+ This assists in reducing config duplication across many
|
|
|
+ contexts which share common settings (e.g. configs for
|
|
|
+ <acronym>HTTP</acronym>, or <acronym>CLI</acronym>, each
|
|
|
+ sharing some characteristics but with their own
|
|
|
+ conflicting values for others) or merely splitting a
|
|
|
+ long configuration across many smaller categorised
|
|
|
+ files. The parameter in this case is an array with a
|
|
|
+ single key "configs" whose value is an array of the
|
|
|
+ files to merge. Note: this means you either pass a
|
|
|
+ literal path, or
|
|
|
+ <command>array("configs"=>array("/path1","/path2"[,...]));</command>.
|
|
|
+ </para>
|
|
|
</listitem>
|
|
|
|
|
|
<listitem>
|
benjamin-gonzales