![]() during environment provisioning or horizontal scaling) new licenses are issued for every newly-created container (e.g.In addition, license lifecycle management is fully automated: Namely, the license is billed only for active containers on an hourly basis for 730 hours per month. The platform seamlessly integrates the cost of the LiteSpeed license in accordance with the fair pay-as-you-go principles. The application deployment process is the same as for any other application server. the notification about the license key expiration in the Actions > Server Log Viewer should be ignored as the leasing is automatically managed by the platform.to ensure container stability, the platform-native redeploy feature should be used instead of the Actions > Version Manager functionality.Note: There are some specifics while working with the platform implementation of the LiteSpeed via the admin panel: To start managing the server, access the Admin Panel with the appropriate button in the Additionally list next to the layer (access credentials are sent via email after the node creation). After creation, you can view the default phpinfo data on the server by clicking Open in Browser next to your LiteSpeed server:Ĥ. WP_PROTECT_LIMIT - sets a limit for the WordPress Brute Force Attack Protection feature ( 0|1|2-1000 10 by default)Ĭonfigure any other required parameters ( cloudlets, disk space, regions, etc.) and proceed with the Create button.ģ.WP_PROTECT - configures an action for the WordPress Brute Force Attack Protection feature ( off|on|drop|deny|throttle|captcha off by default).WAF - enables ( true) or disables ( false, by default) Web Application Firewall with the Comodo default ruleset.REDIS_ENABLED - enables ( true) or disables ( false, by default) object caching with Redis.You need to manually add this variable and restart the server to redefine the value ![]() The variable is hidden by default as the platform sets this value equal to the number of available CPU cores (usually ensures the best operability). LSWS_MAX_CHILDREN - redefines the maximum children process limit for the server.JELASTIC_AUTOCONFIG - enables ( enabled, by default) or disables ( disabled) autoconfiguration of the LiteSpeed worker processes count based on the allocated RAM and number of CPU cores.You may want to adjust some dedicated environment variables to customize your LiteSpeed Web Server: support of the caching plugins, cutting-edge anti-DDoS features, built-in WAF security, etc.WordPress, Magento, Drupal, Joomla, etc.) individual optimization for the most popular hosting platforms (e.g.full compatibility with commonly used Apache features including mod_rewrite.an event-driven architecture (like NGINX) consumes fewer resources than Apache process-based model, ensuring better performance with minimum memory and CPU usage.The feature-rich structure of the LiteSpeed application server includes the following specifics: ![]() It is built based on the best practices of the PHP hosting, utilizing the benefits of both Apache and NGINX implementations, and integrating its own optimizations. ![]() The LiteSpeed Web Server is a high performance and low memory consumption PHP web server with high scalability. However, a public IP address is required to bypass the Shared Load Balancer and work directly with the server over HTTP/3. The LiteSpeed Web ADC stack is HTTP/3 ready with the feature support enabled by default. ![]()
0 Comments
Leave a Reply. |