Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:php:per-user-php-ini [2018/07/02 14:14]
Lisa Clarke [Troubleshoot] Proofreading
litespeed_wiki:php:per-user-php-ini [2018/09/14 16:03]
Michael Alegre [Notes]
Line 107: Line 107:
 ===== Notes ===== ===== Notes =====
   * **PHP suEXEC MUST BE ENABLED IN LSWS.**   * **PHP suEXEC MUST BE ENABLED IN LSWS.**
-  * Make sure the php.ini file is readable by the suEXEC ​user.+  * Make sure the php.ini file is readable by the **Run As User** ​user.
   * Option 3 can be used along with options 1, 2, or 4 without conflicts. However, this should rarely be needed.   * Option 3 can be used along with options 1, 2, or 4 without conflicts. However, this should rarely be needed.
   * Option 4 takes precedence over options 1 and 2 should they be used at the same time.   * Option 4 takes precedence over options 1 and 2 should they be used at the same time.
   * Changes in the php.ini will not be picked up until new PHP process starts. The php.ini is read for the first time when a PHP process starts.   * Changes in the php.ini will not be picked up until new PHP process starts. The php.ini is read for the first time when a PHP process starts.
-  * Per-user php.ini files are not compatible with [[http://​www.litespeedtech.com/​products/​litespeed-sapi/​php/​suexec-daemon-mode|suEXEC ​Daemon mode]]. Our [[http://​www.litespeedtech.com/​products/​litespeed-sapi/​php/​guide-to-suexec-setups|two other PHP suEXEC setups]] both support per-user php.ini.+  * Per-user php.ini files are not compatible with [[http://​www.litespeedtech.com/​products/​litespeed-sapi/​php/​suexec-daemon-mode|Daemon mode]]. Our [[http://​www.litespeedtech.com/​products/​litespeed-sapi/​php/​guide-to-suexec-setups|two other PHP process modes]] both support per-user php.ini.
   * For native LSWS installs, these variables ($VH_ROOT, $VH_NAME, $VH_USER, etc.) need to be inside of a Virtual Host External App Environment Section, and not inside the general Server External App Environment Section. This is because the variables are expanded on start up, so the VH_* variables cannot be expanded during server level configurations.   * For native LSWS installs, these variables ($VH_ROOT, $VH_NAME, $VH_USER, etc.) need to be inside of a Virtual Host External App Environment Section, and not inside the general Server External App Environment Section. This is because the variables are expanded on start up, so the VH_* variables cannot be expanded during server level configurations.
  
  • Admin
  • Last modified: 2020/01/01 15:13
  • by George Wang