We're rolling out a whole new line of virtual hosts for different set ups and functions. Two days ago we announced the release of a template for setting up Enterprise or OpenLiteSpeed with WP Super Cache. Today we have a template for setting up LiteSpeed Web Server as a reverse proxy to a backend server. My first time using the template (I don't create the templates, I do the documentation), I set it up in a grand total of 6:37.8. That's what I call quick and easy. Read the rest of this entry »
LiteSpeed Web Server has a lot of settings. It's true. We know. These settings are helpful to tweak and fine tune your server. But sometimes, when you're just getting started with a new environment, feature, or application, all those settings can be overwhelming. That is why we are introducing custom virtual host templates. These templates give you virtual hosts ready to perform different functions or use with different applications. You can still customize and tune different parts of the setup if you want, but these templates will give you a workable LSWS for your particular function in just a few quick and easy steps. Read the rest of this entry »
HostingCon is coming (June 17-19). We’ll be there and we’d love to meet you. Read the rest of this entry »
blished two new Twitter accounts — @lswsrelease and @openlswsrelease — for those of you who only want to be contacted when there's a new release. This will be a streamlined way to keep up with your LiteSpeed software updates and not get distracted. (Because the point of Twitter is to not get distracted, right?)
LiteSpeed Web Server version 4.2.3 brings in some simple, but long-requested features.
One of the most
common questions we get goes something like this: “I have a forum with 3,000 users and the VPS license says it has a limit of 500 concurrent connections. That's not enough for me, right?” Actually, 50 concurrent connections is probably enough for you. This misconception stems from a misunderstanding as to what a concurrent connection is. In this post, I will try to address this misunderstanding. Read the rest of this entry »