4/18/2024 0 Comments Increase download speed php cpanel![]() ![]() ![]() In LSWS Web Admin Console, change php external app from Environment: PHPRC=$VH_ROOT/public_html (user based) to Environment: PHPRC=$DOC_ROOT (domain based), if the user has a full php.ini at /home/USER1/public_html/php.ini.If you prefer for each subdomain to have it's own php.ini, for example /home/USER1/public_html//php.ini, instead of relying on the user-level /home/USER1/public_html/php.ini, you can do the following: All such domains will use doc_root/php.ini. One user may have many subdomains or addon domains, which may be located in subdirectories under the main domain's document root. For these settings, you will need to use PHPRC or PHP_INI_SCAN_DIR to define the php.ini for each user. However, some PHP settings are not supported by cPanel MultiPHP Manager, such as allow_url_fopen and allow_url_include. Most of the time, you should use cPanel's MultiPHP Manager to handle overriding PHP values. However, this is not recommended, and you are encouraged to just use cPanel MultiPHP INI Editor. If at any time you explicitly want to apply /home/$USER/public_html/.user.ini, regardless of the cPanel default multi-file implementation, you will need to use PHP_INI_SCAN_DIR to manually set it up as instructed earlier in this documentation. You must use cPanel MultiPhP INI Editor GUI to make any changes for your test. Please also keep in mind that you cannot manually change settings in any of the files through SSH. LiteSpeed is compatible with cPanel MultiPHP INI Editor out of the box with no extra configuration required. user.ini.ĬloudLinux mod_lsapi for Apache uses. A user may change the handler at some point, and the three files will be updated accordingly to ensure the cPanel MultiPHP INI Editor settings will continue to apply.Īpache PHP CGI and PHP-FPM use. This is because different PHP handlers will use different files to apply the settings. You have probably noticed that the same changes are being saved to three different files at the same time. Therefore, adding an individual include file for that host Apache configuration is normally recommended as described as above. This method is also applicable to a control panel environment such as cPanel, but it will modify the behavior of any virtual hosts using this external application. PHPRC in the WebAdmin Console ¶ĭefining the PHPRC environment variable in the WebAdmin console allows you to use a variable that can set a standard location for the php.ini file in each virtual host. PHPRC will replace your ea-phpxx php.ini with a new php.ini at specified user's location, while PHP_INI_SCAN_DIR will load default ea-phpxx php.ini as well as aditional *.ini. To apply per-user php.ini to all virtual hosts globally, you can use either PHPRC or PHP_INI_SCAN_DIR at LSWS Web Admin Console > PHP > Environment as well as LSWS Web Admin Console > External App > lsphpxx -> Environment(need to apply to all lsphpxx). To apply per-user php.ini to all virtual hosts globally ¶ To apply per-user php.ini to any particular apache virtual host, you can use PHPRC or PHP_INI_SCAN_DIR in that cPanel apache virtual host include file. To apply per-user php.ini to all cPanel virtual hosts globally, you can use PHPRC or PHP_INI_SCAN_DIR in LiteSpeed PHP Environment configuration. If using CloudLinux and CL PHP Selector, please refer to CloudLinux documentation. To enable a per-user php.ini, you can use either PHPRC or PHP_INI_SCAN_DIR. ![]() LiteSpeed Memcached LiteSpeed Memcached.LSCache Developers Guide LSCache Developers Guide.LSCache Without a Plugin LSCache Without a Plugin.Third Party Plugins Third Party Plugins.To apply per-user php.ini to a particular virtual host.PHP_INI_SCAN_DIR in the WebAdmin Console.To apply per-user php.ini to all virtual hosts globally.Per-User php.ini Per-User php.ini Table of contents.WHM LiteSpeed Plugin WHM LiteSpeed Plugin.External Applications External Applications.LiteSpeed Web Server LiteSpeed Web Server.You can enable the Gzip compression by editing the Nginx virtual host configuration file: nano /etc/nginx/sites-enabled/your-domain. We also recommended to configure NGINX so that it only compresses large files and avoids smaller files. It utilizes less network bandwidth and improves the page load time for slow connections, while also reducing your file size by up to 70%. This will reduce the amount of time required to transfer a resource from the server to a browser. Gzip compression used to reduce the size of files request by client’s web browser. If you want to increase your website speed, Gzip compression is considered a high-priority recommendation by site speed test tools. Configure Worker Processes to Improve Speed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |