Differences

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

--- litespeed_wiki:php:per-user-php-ini [2018/07/02 11:17]
qtwrk [Notes]
+++ litespeed_wiki:php:per-user-php-ini [2019/08/29 20:44]
Jackson Zhang
@@ Line 58: / Line 58: @@
 **Note:**
    * Using this method will cause LSWS to ignore any global php.ini files and only use the user-defined php.ini. However, if no user-defined php.ini found, LSWS will still use global php.ini
+Starting from LSWS 5.3.x, LSWS may automatically configure external applications and script handlers for control panels, hence it may not have external applications or script handlers anymore. If you want to define PHPRC environment variable for all external applications, you can use ''PHP'' tab:
+{{ :litespeed_wiki:php:lsws-5.3.x-php-tab.png?800 |}}
 ===== 3. Define PHP_INI_SCAN_DIR at the Server Level in the WebAdmin Console =====
@@ Line 78: / Line 82: @@
   * This method is not recommended if you replace Apache with suPHP. When replacing Apache with suPHP, the PHPRC environment variable is recommended.
   * The PHP_INI_SCAN_DIR environment variable is available for PHP 5.2.7 and up.
+Starting from LSWS 5.3.x, LSWS may automatically configure external applications and script handlers for control panels, hence it may not have external applications or script handlers anymore. If you want to define ''PHPRC'' environment variable for all external applications, you can use ''PHP'' tab.
 ===== 4. Define PHPRC in Apache Configs =====
@@ Line 104: / Line 110: @@
 This directive is supported since PHP LSAPI version V6.10.
+===== 7. Override External Application Environment Variables =====
+The special Apache directive ''LS_EXTAPP_ENV'' can be used on cPanel or other control panel environments to override External application environment variables.
+If you have set up ''PHP_INI_SCAN_DIR'' in step 3, and ''PHP_INI_SCAN_DIR'' in step 1, LSWS will use ''PHP_INI_SCAN_DIR'' from an external app environment instead of using Apache directives. Starting from LSWS 5.3.4, you can override this external app environment using a new special Apache directive: ''LS_EXTAPP_ENV''. Place the directive in the Apache virtual host include file, like so:
+For example, say you have set the following in an external app environment:
+  PHP_INI_SCAN_DIR=/home/USER1/public_html
+If you want to override it to another location, such as ''/home/USER1/data'', you can add the following to the Apache virtual host include file:
+  <IfModule Litespeed>
+  LS_EXTAPP_ENV PHP_INI_SCAN_DIR=/home/USER1/data/
+  </IfModule>
 ===== Notes =====
   * **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 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.
-  * 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.
+===== 8 Supports MultiPHP INI Editor for cPanel out of the box =====
+When a user login to cPanel and edit his own php settings through [[https://documentation.cpanel.net/display/82Docs/MultiPHP+INI+Editor+for+cPanel|cPanel MultiPHP INI Editor]] (cPanel >> Home >> Software >> MultiPHP INI Editor), cPanel MultiPHP INI Editor will save changes to three files in /home/$USER/public_html/:   php.ini file, the user.ini file, and .htaccess file.
+For example:
+  [/home/blogu1/public_html]# ll
+  -rw-r--r--  1 blogu1 blogu1 4484 Aug 29 12:25 .htaccess
+  -rw-r--r--  1 blogu1 blogu1  576 Aug 29 12:25 php.ini
+  -rw-r--r--  1 blogu1 blogu1  582 Aug 29 12:25 .user.ini
+in .htaccess
+  # BEGIN cPanel-generated php ini directives, do not edit
+  # Manual editing of this file may result in unexpected behavior.
+  # To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor)
+  # For more information, read our documentation (https://go.cpanel.net/EA4ModifyINI)
+  <IfModule php7_module>
+   php_flag display_errors Off
+   php_value max_execution_time 57
+   php_value max_input_time 60
+   php_value max_input_vars 1000
+   php_value memory_limit 33M
+   php_value post_max_size 8M
+   php_value session.gc_maxlifetime 1440
+   php_value session.save_path "/var/cpanel/php/sessions/ea-php72"
+   php_value upload_max_filesize 2M
+   php_flag zlib.output_compression Off
+  </IfModule>
+  <IfModule lsapi_module>
+   php_flag display_errors Off
+   php_value max_execution_time 57
+   php_value max_input_time 60
+   php_value max_input_vars 1000
+   php_value memory_limit 33M
+   php_value post_max_size 8M
+   php_value session.gc_maxlifetime 1440
+   php_value session.save_path "/var/cpanel/php/sessions/ea-php72"
+   php_value upload_max_filesize 2M
+   php_flag zlib.output_compression Off
+  </IfModule>
+  # END cPanel-generated php ini directives, do not edit
+in .user.ini
+  ; cPanel-generated php ini directives, do not edit
+  ; Manual editing of this file may result in unexpected behavior.
+  ; To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor)
+  ; For more information, read our documentation (https://go.cpanel.net/EA4ModifyINI)
+  [PHP]
+  display_errors = Off
+  max_execution_time = 57
+  max_input_time = 60
+  max_input_vars = 1000
+  memory_limit = 33M
+  post_max_size = 8M
+  session.gc_maxlifetime = 1440
+  session.save_path = "/var/cpanel/php/sessions/ea-php72"
+  upload_max_filesize = 2M
+  zlib.output_compression = Off
+in  php.ini
+  ; cPanel-generated php ini directives, do not edit
+  ; Manual editing of this file may result in unexpected behavior.
+  ; To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor)
+  ; For more information, read our documentation (https://go.cpanel.net/EA4ModifyINI)
+  display_errors = Off
+  max_execution_time = 57
+  max_input_time = 60
+  max_input_vars = 1000
+  memory_limit = 33M
+  post_max_size = 8M
+  session.gc_maxlifetime = 1440
+  session.save_path = "/var/cpanel/php/sessions/ea-php72"
+  upload_max_filesize = 2M
+  zlib.output_compression = Off
+Why the same changes are being saved to three different files at the same time? It is because of different php handler will use different files to apply the settings. User may change handler sometimes and three files keeping the same changes will make sure cPanel MultiPHP INI Editor settings will apply regardless of handler change.
+For Apache SuPHP, it will use php.ini. For Apache PHP CGI and PHP-fpm, it will use .user.ini. For CloudLinux mod_lsapi for Apache, it will use .htaccess. LiteSpeed will use settings in .htaccess.
+LiteSpeed will be compatible with cPanel MultiPHP INI Editor out of box without extra configuration required. However, if you explicitly want to apply /home/$USER/public_html/php.ini regardless of the cpanel default multi-files implementation, you will need to use ''PHP_INI_SCAN_DIR'' to manually set up as instructed earlier in this wiki, but it is not recommended to do so and you are encouraged to just use cPanel MultiPHP INI Editor ways of implementation.
 ===== Troubleshoot =====
-  * Some PHP extension missing after loaded with per user php.ini, for example **Your PHP installation appears to be missing the MySQL extension which is required by WordPress.**
+Some PHP extensions are missing after being loaded with per user ''php.ini'', for example
+<code>Your PHP installation appears to be missing the MySQL extension which is required by WordPress.</code>
-This is because once custom php.ini is loaded , the default php.ini will be ignored , therefore extensions will not be loaded.
+This is because once custom php.ini is loaded, the default php.ini will be ignored. Therefore, extensions will not be loaded.
-To resolve this problem , the easier way to go is copy the content of default php.ini into custom php.ini by following command:
+The easiest way to resolve this problem is to copy the contents of the default php.ini into the custom php.ini by the following command:
 <code>cat /opt/cpanel/ea-phpXX/root/etc/php.ini /opt/cpanel/ea-phpXX/root/etc/php.d/*.ini > /path/to/php.ini</code>
-Please replace ''ea-phpXX'' and ''/path/to/php.ini'' to corresponding version and path.
+Please replace ''ea-phpXX'' and ''/path/to/php.ini'' with the appropriate version and path.
-Verify the php.ini content and restart lsws if necessary, as change in php.ini will not take effect until new PHP process starts. The php.ini is read for the first time when a PHP process starts.
+Verify the php.ini content and restart LSWS if necessary, as a change in php.ini will not take effect until a new PHP process starts. The php.ini is read for the first time when a PHP process starts.