With this feature, you can have a single tenant, but for servers in the tenant, you can have multiple data directories on severs, like one data path backed by SSD to keep recent data; one data path backed by HDD to keep older data, to bring down the cost of keeping long term historical data. all links in the conf.d directories are pointing to an ini-file in mods-available. Thats allows me to enable/disable modules without editing any ini-file only with linking to mods-available folder. Thats the only reason why I am asking. If it is not possible with arch linux, so I have to deal with it and do it in the more complex way by editing each php.ini file manually. Cause: The environment variable PHP_INI_SCAN_DIR could only be set to a single directory name. Consequence: A software collection dependent on the php54 collection cannot use an additional directory for configuration files. Fix: PHP has been patched to allow multiple directory names in the PHP_INI_SCAN_DIR environment variable, as a colon separated list. Result: A dependent collection can now set PHP_INI_SCAN_DIR appropriately, allowing use of multiple configuration directories. Clone Of:1058161Environment:Last Closed:2014-06-04 07:18:01 UTCTarget Upstream Version:Have you experienced this issue?Rate the importance of this bug to you:Are you using the same PHP version?Are you using the same operating system? PatchesAdd a Patch Pull RequestsAdd a Pull Request HistoryThe configuration file (php.ini) is read when PHP starts up. For the server module versions of PHP, this happens only once when the web server is started. For the CGI and CLI versions, it happens on every invocation. php.ini is searched for in these locations (in order):
If php-SAPI.ini exists (where SAPI is the SAPI in use, so, for example, php-cli.ini or php-apache.ini), it is used instead of php.ini. The SAPI name can be determined with php_sapi_name().
Using environment variables can be used in php.ini as shown below. Example #1 php.ini Environment Variables ; PHP_MEMORY_LIMIT is taken from environment memory_limit = ${PHP_MEMORY_LIMIT} The php.ini directives handled by extensions are documented on the respective pages of the extensions themselves. A list of the core directives is available in the appendix. Not all PHP directives are necessarily documented in this manual: for a complete list of directives available in your PHP version, please read your well commented php.ini file. Alternatively, you may find ยป the latest php.ini from Git helpful too. Example #2 php.ini example ; any text on a line after an unquoted semicolon (;) is ignored [php] ; section markers (text within square brackets) are also ignored ; Boolean values can be set to either: ; true, on, yes ; or false, off, no, none register_globals = off track_errors = yes ; you can enclose strings in double-quotes include_path = ".:/usr/local/lib/php" ; backslashes are treated the same as any other character include_path = ".;c:\php\lib" Since PHP 5.1.0, it is possible to refer to existing .ini variables from within .ini files. Example: open_basedir = ${open_basedir} ":/new/dir". Scan directoriesIt is possible to configure PHP to scan for .ini files in a directory after reading php.ini. This can be done at compile time by setting the --with-config-file-scan-dir option. In PHP 5.2.0 and later, the scan directory can then be overridden at run time by setting the PHP_INI_SCAN_DIR environment variable. It is possible to scan multiple directories by separating them with the platform-specific path separator (; on Windows, NetWare and RISC OS; : on all other platforms; the value PHP is using is available as the Within each directory, PHP will scan all files ending in .ini in alphabetical order. A list of the files that were loaded, and in what order, is available by calling php_ini_scanned_files(), or by running PHP with the --ini option. |