Differences

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

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:cloudlinux:installation [2015/11/06 22:13]
Michael Alegre
litespeed_wiki:cloudlinux:installation [2018/09/14 15:59] (current)
Michael Alegre
Line 11: Line 11:
 For installation/​configuration of PHP, you may have already used CloudLinux PHP Selector for your customers. LiteSpeed works very well with PHP Selector and you can certainly continue to use it as you wish. Please check [[litespeed_wiki:​cloudlinux:​php-selector|this instruction]] get PHP Selector configured. For installation/​configuration of PHP, you may have already used CloudLinux PHP Selector for your customers. LiteSpeed works very well with PHP Selector and you can certainly continue to use it as you wish. Please check [[litespeed_wiki:​cloudlinux:​php-selector|this instruction]] get PHP Selector configured.
  
-Generally speaking, you have to enable [[https://​www.litespeedtech.com/​docs/​webserver/​config/​general#​phpSuExec|PHP SuEXEC]] in shared hosting environment. Make sure to set it "Yes" ​or "User's Home Directory Only". You should use PHP SuEXEC ​Worker mode or PHP SuEXEC ​ProcessGroup mode for CloudLinux since PHP SuEXEC ​Daemon mode is incompatible with PHP Selector. check [[litespeed_wiki:​php:​which_php_setup_am_i_using#​php_suexec_setups|here]] for setup details. Since PHP SuEXEC ​Worker mode is incompatible with Opcode Cache, ​SeEXEC ​ProcessGroup mode may be good for relatively busy sites and take advantage of PHP Opcode Cache to speed up the loading time. +Generally speaking, you have to enable ​**[[https://​www.litespeedtech.com/​docs/​webserver/​config/​general#​phpSuExec|PHP SuEXEC]]** in shared hosting environment. Make sure to set it ''​Yes'' ​or ''​User's Home Directory Only''​. You should use PHP Worker mode or PHP ProcessGroup mode for CloudLinux since PHP Daemon mode is incompatible with PHP Selector. check [[litespeed_wiki:​php:​which_php_setup_am_i_using#​php_suexec_setups|here]] for setup details. Since PHP Worker mode is incompatible with Opcode Cache, ProcessGroup mode may be good for relatively busy sites and take advantage of PHP Opcode Cache to speed up the loading time. 
  
-A good and recommended practice is to set Apache Offset Port, such as 2000 or other numbers you prefer, ​ during the installation process for testing purpose, which means running both Apache and LiteSpeed server ​parallelly. Apache will run on port 80 while LiteSpeed will run at port 2080 instead, which will give you opportunity to test LiteSpeed without impacting your real live traffic. If the test runs successfully,​ you can reset Apache Offset Port to "​0"​ and switch over to LiteSpeed to let LiteSpeed to handle your real traffic. ​+A good and recommended practice is to set Apache Offset Port, such as 2000 or other numbers you prefer, ​ during the installation process for testing purpose, which means running both Apache and LiteSpeed server ​in parallel. Apache will run on port 80 while LiteSpeed will run at port 2080 instead, which will give you opportunity to test LiteSpeed without impacting your real live traffic. If the test runs successfully,​ you can reset Apache Offset Port to "​0"​ and switch over to LiteSpeed to let LiteSpeed to handle your real traffic. ​
  
 For more detailed configuration on LVE, CageFS or PHP Selector, please check [[http://​docs.cloudlinux.com/​index.html|CloudLinux documentations]] For more detailed configuration on LVE, CageFS or PHP Selector, please check [[http://​docs.cloudlinux.com/​index.html|CloudLinux documentations]]
  
 
litespeed_wiki/cloudlinux/installation.txt · Last modified: 2018/09/14 15:59 by Michael Alegre