4.0 road map

[Tony]

Originally Posted by IrPr

There are a lot of advantages in performances and scability with LSWS but one of the most disadvantages is poor server status againts another webservers
Apache has a server-status with minimal reports but lighttpd's server-status is great!

I would strongly suggest Server-status feature which has a lot of requests

I have to agree with you there. The latest beta has improved the status page quite a bit it's a lot easier to use now. But the one thing that is lacking is a quick way to see where all the requests are going to. It's great there are 5 requests to domain.com but where on domain.com?

It would also be neat if somehow a basic server-status could match up with the control panels way of showing it. That way in cPanel for example the apache status link still shows something but this time coming from litespeed. But I don't know how feasible that would be but then it would make it really a drop in.


Still love litespeed a lot more than Apache though

[anewday]

A better status page has been requested many times on this forum. I would also like the Apache Status page in WHM to be integrated with Litespeed's.

[TomBG]

Originally Posted by mistwang

We will add an option to store vhost template members in a standalone flat text file.

This would be amazing. The only reason we're sticking with Apache conf's is because our hosting admin software uses templates for each virtualhost, and changing over to your XML format would be a hassle.

Any ETA on 4.0 release? Is anyone using 4.0 in production? I have about 10-20 web servers I'd like to migrate over and we just got a FreeBSD binary to play with.

[Tony]

Originally Posted by TomBG

Any ETA on 4.0 release? Is anyone using 4.0 in production? I have about 10-20 web servers I'd like to migrate over and we just got a FreeBSD binary to play with.

We use it on all our servers which is shared hosting. So for us that is the production level.

[Guermo]

Have you had any issues since making the upgrade from to RC1? Do you think with the added features and easier transition from Apache 2.2 than you would get with version 3.3.24 makes up for any instability or bugs there might be?
Is v.4.0RC1 quite a bit easier to install and configure, especially with cPanel?

[Tony]

Originally Posted by Guermo

Have you had any issues since making the upgrade from to RC1? Do you think with the added features and easier transition from Apache 2.2 than you would get with version 3.3.24 makes up for any instability or bugs there might be?
Is v.4.0RC1 quite a bit easier to install and configure, especially with cPanel?

We're running RC1 without issue. We only use lsws and do not have Apache running at all. Everything runs great and cPanel plays nice with lsws so it does not know of anything.

The only headache we have is with frontpage as cPanel changed it's scripts recently for changing permissions and I have yet to figure them all out so that I can modify them to work with lsws. With frontpage use going down every day it's not a huge deal at this point for us.

[Guermo]

Do you think v. 4.0RC1 would be easier to install and configure than version 3.3.24?

[Tony]

Originally Posted by Guermo

Do you think v. 4.0RC1 would be easier to install and configure than version 3.3.24?

The only difference between them is with 3.3.24 we'd have to run Apache still to proxy back shtml files for ssi. With 4.0RC1 we do not have to do this so using the whm plugin you can build the matching php then have the plugin switch lsws to port 80 and shutoff apache.

[Guermo]

OK, thanks tony

[anewday]

option to backup and version control configuration file.

Will this be in 4.1?