New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for LiteSpeed server #2622
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues. |
Came here while Googling for Lando with Litespeed |
Is this taken into consideration? |
+1 from me as well. |
+1 from me as well |
+1 as well ... using OLS in docker, thats the only reason why I dont switch to Lando full-time |
+1 OLS is neccessary at today time |
Here's some usage data from our Telemetry page: Web Server
It seems that LiteSpeed is as popular as nginx. |
+1 from me. Developing a mixture of Drupal and Wordpress. |
+1 from me. |
will also love this ..+1 |
+1 from me. |
Another +1 here :) |
+1 |
Please explain your request and its importance in the form of a user story.
As a lando user who works with Drupal sites that have high traffic, I would like to develop using the LiteSpeed or OpenLiteSpeed web server instead of using Apche or Nginx
Please provide some detail on how lando can help solve this problem
Provide an option for using the Drupal recipe via LiteSpeed.
Is your feature request related to a problem? Please describe.
Even though LiteSpeed is very compatible with Apache, using the actual software that's used in production helps avoiding many questions when debugging. I also suspect that using LiteSpeed for development with Lando, instead of using Apache, would take less resources. I haven't test this assumption though.
Describe the solution you'd like
Describe alternatives you've considered
The most obvious alternative is to use Apache and hope there are no differences.
Another alternative would be using a custom recipe with a LiteSpeed container; however, I haven't tried that.
The text was updated successfully, but these errors were encountered: