Installing with Cpanel
- Thread starter Suxen
- Start date
After many days of proxying from apache to lsws, there are still something of interest though.
In "Use apache config" mode, does lsws capable of running php in suExec mode, or do we need to tinker with deploying lsphp for each vhost through External App setting in VH template section?
When running lsws on port 80, how to make bandwidth calculation and overusage suspension work in cPanel?
In "Use apache config" mode, does lsws capable of running php in suExec mode, or do we need to tinker with deploying lsphp for each vhost through External App setting in VH template section?
When running lsws on port 80, how to make bandwidth calculation and overusage suspension work in cPanel?
Currently, you need to use the VH template if you want PHP suEXEC. We will add a feature to address this later.
When run LSWS off apache configuration, LSWS logs bandwidth usage into the same bandwidth log file produced by mod_log_byte in Apache. So Cpanel can calculate the bandwidth usage as usual. No sure how cPanel suspend an account with Apache though.
When run LSWS off apache configuration, LSWS logs bandwidth usage into the same bandwidth log file produced by mod_log_byte in Apache. So Cpanel can calculate the bandwidth usage as usual. No sure how cPanel suspend an account with Apache though.
Cool. Is there any ETA on this?
Real cool.
The way that cPanel suspends account is simply to put a rewrite rule into user's public_html/.htacces file:
Well, seem like LSWS is getting there to be compatible with a leading control panel. It's going to be a very nice milestone marketing wise. 
To make the migration more seamless, by initially proxying requests from cPanel's apache install to lsws, I wonder if there's any way to also forward client's ip addresses to lsws as well? This will make many web apps that rely on client's ip addresses to work as usual and server operator having a piece of mind of watching lsws working in their real production env.
Thanks.
Real cool.
The way that cPanel suspends account is simply to put a rewrite rule into user's public_html/.htacces file:
Code:
# cat .htaccess
RedirectMatch .* http://main.server.host/suspended.page/
Options -Includes -Indexes -ExecCGITo make the migration more seamless, by initially proxying requests from cPanel's apache install to lsws, I wonder if there's any way to also forward client's ip addresses to lsws as well? This will make many web apps that rely on client's ip addresses to work as usual and server operator having a piece of mind of watching lsws working in their real production env.
Thanks.
mistwang said:
Proxying through Apache will not give you the performance advantage provided by LSWS.
There are also a couple other servers that apache were replaced by LSWS completely. One of them used to run apache2 then replaced by lighttpd and then again by lsws.
Where exactly would this code be posted?
Hi! This is exactly what I was looking for.. (shocking)! However, I am not sure where the register code would be posted to enable the OS commerce I recently installed??
Yes it works if I use this in .htaccess
(i know, it shouldn't be that way but some people just don't bother to improve their old codes because they _work_ )
But since we've got quite a few people putting this in user's php.ini file in their www directory:
Is there anyway to make user's php.ini being recognized by lsws/php?
Thanks.
Code:
php_value register_globals 1But since we've got quite a few people putting this in user's php.ini file in their www directory:
Code:
register_globals = OnThanks.
I can't seem to get into the directory where osCommerce is installed. I created it as a separate directory (ex. ralphcherman.com/shop) and the admin panel is not allowing me to access. Is there a way to get into this to create the .htaccess file from my cPanel FTP or something? Thanks for all your help, I really appreciate it.