Support

Suxen · #1 03-04-2006, 02:12 PM

After reading the site documentation, FAQ, and searching the forum, I have only come across a few references to those using LiteSpeed Web Server, and Cpanel. What I'm looking for is a more indepth insight into the possible integration - or compatiblity - with webserver control panel software, namely Cpanel, but how it interacts with others could be equally interesting for someone else who may stumble upon this thread wondering the same thing.

I'll make this a short and sweet post: will installing this on a server with Cpanel cause any problems, or is it relatively painless? Assuming it can be done:

1) Will it overwrite the existing /usr/local/apache directory? If so, is it easy enough to revert?
2) Assuming 1) is false, how will newly added subdomains from apache work? They are all saved into /usr/local/apache/conf/httpd.conf
3) Never end a list on two.

Thanks for any information you can provide. It looks like an interesting project, and squeezing the last drop out of performance out of a server is always appealing but sadly it seems most of the technologies out there (such as lighttpd) will cause Cpanel to die a nasty and horrible death (supremely break it).

Thanks for reading,
-Suxen

mistwang · #2 03-04-2006, 07:12 PM

Answers to your questions:

1. No, you can install LSWS wherever you want, /usr/local/lsws or /opt/lsws is recommended location.

2. LSWS can watch and automatically reload httpd.conf if you let LSWS to use Apache's httpd.conf directly.

LSWS is mod_rewrite compatible and has same .htaccess support, so it make migration between Apache and LSWS painless.

The easiest way for Cpanel integration probably is let LSWS ready httpd.conf directly, but it may not work 100% perfectly, but should be very close. One user reported that it works with Cpanel.
Other than that, you can try our vhost template feature if it is for mass hosting.

We'd like to make LSWS Cpanel integration flawlessly, so, feel free to ask for help here if you met any problem. :-)

Suxen · #3 03-04-2006, 10:38 PM

Many thanks for your response, it was very informative and useful! It's great that someone is finally trying to work for both compatibility and optimization of a webserver! Great work guys, long may it continue.

My LSWS + Cpanel project begins tomorrow, wish me luck :twisted:

pizzaman · #4 03-25-2006, 09:38 AM

Suxen,

I'd also be interesting in your success case.

Recently what I've just done were proxying some heavy php sites
from cPanel's apache to lsws, and this cuts down server load by
a good margin. I used to do that with lighttpd earlier but after a day
I found that lighty couldn't process .htacess and apache's rewrite
rules so it was a no go. After the switch, things went very smoothly.

Suxen · #5 03-25-2006, 04:31 PM

I'm going to confess I've been slacking, just this once

I had to move from one server company to another due to various reasons, so I haven't actually gotten around to it as such yet. :roll:

But I do plan to give it a shot this following week and see how things turn out. Well done on the proxying idea, I've been wanting to find a decent way to cut load on my server for ages but looking at all the available choices when combined with CPanel made it all seem too much hassle until finding LSWS.

Will be interesting to see how CPanel handles things with Apache is completely replaced for sure.

pizzaman · #6 03-25-2006, 08:05 PM

cPanel's setting allow for overriding php.ini (like setting register_global on) in users' home dirs. I'm not sure if this can be done with lsws's php or not.

Good luck, and please keep us posted.

mistwang · #7 03-25-2006, 08:43 PM

Yes, php configuration overriding is supported with LSPHP. :-)

pizzaman · #8 03-26-2006, 12:52 AM

Quote:

Originally Posted by mistwang

Yes, php configuration overriding is supported with LSPHP. :-)

I used php that comes bundled with lsws, and putting php.ini (with register_global on flag as in usual cPanel box) in user's www path but php didn't pick up that override. I've tried that and it didn't work out but perhaps I missed something.

mistwang · #9 03-26-2006, 04:04 AM

htacess support has not been properly turned, you need to turn it on at both server and vhost level.

pizzaman · #10 03-26-2006, 05:40 AM

Quote:

Originally Posted by mistwang

htacess support has not been properly turned, you need to turn it on at both server and vhost level.

Yes it works if I use this in .htaccess

Code:

php_value register_globals 1

(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:

Code:

register_globals = On

Is there anyway to make user's php.ini being recognized by lsws/php?

Thanks.