When we initially planned to migrate to LiteSpeed we thought it would take about a month. So we didn’t just replace Apache but got rid of Openresty too, reducing the software stack used to process requests and thus increasing performance. That was great news to us since we didn’t have to reimplement our current vhost management process. They were happy to help and implement it in the development branch. Turns out, we were lucky as they were already developing LiteSpeed version 5.4. We contacted LiteSpeed support, explained our current setup and the fact that we want to make it dynamically managed.
#Litespeed web server buy update
However, we wanted to implement fully dynamic management which doesn’t need to reload services in order to update the configuration, as we did with the OpenResty setup. Originally, LiteSpeed is configured using config files. Then it is passed on to the Apache web server.
OpenResty retrieves said data when a web request is received. This is how it works: vhost data is saved in Redis. However, Hostinger uses a custom hosting panel – hPanel – which has dynamic vhost management based on Redis and OpenResty + custom LUA scripts. LiteSpeed supports popular hosting provider panels such as WHM/cPanel, DirectAdmin, Plesk, and more.
When compared to Apache, it has a few advantages:īut that’s just the tip of the iceberg! hPanel LiteSpeed is a drop-in replacement for Apache with. At the beginning of 2019, Hostinger decided to try LiteSpeed Web Servers (LSWS) as the main web server instead of Apache.
0 kommentar(er)
