From OpenLiteSpeed Wiki
Revision as of 21:06, 22 September 2014 by Marmstrong
This wiki covers the generic steps for registering an OpenLiteSpeed module. These steps should allow you to add any module you wish, though configuration of modules may vary.
For this guide, we assume you already have downloaded a copy of the module source code and have a working installation of OpenLiteSpeed 1.3 or higher. Module support is only available in versions 1.3 or higher.
In this guide we will be using the OpenLiteSpeed cache module as our example.
- 1 Find the module source code
- 2 Run make with the module source code
- 3 Copy the dynamic library MODULE_NAME.so to the OpenLiteSpeed modules directory
- 4 Add the module by going to WebAdmin console > Configuration > Server > Modules > Add
- 5 Enter the name of the module as "MODULE_NAME"
- 6 Copy in the parameters
- 7 Save the module settings
- 8 Make sure the module priority does not conflict with other modules
- 9 Further configure the module at different levels
Find the module source code
Source code for modules provided by LiteSpeed is located in the decompressed OpenLiteSpeed download package (not in your OpenLiteSpeed installation) under the
make with the module source code
This should create a dynamic library called
Copy the dynamic library
MODULE_NAME.so to the OpenLiteSpeed
cp cache.so /usr/local/lsws/modules
Add the module by going to WebAdmin console > Configuration > Server > Modules > Add
Enter the name of the module as "MODULE_NAME"
Copy in the parameters
Most modules are configured using parameters entered into the Parameters setting. These settings should be discussed in the module's documentation.
Save the module settings
Make sure the module priority does not conflict with other modules
Conflicting module priorities can cause erratic functionality. Leaving priorities as "Not Set" should be safe for most use cases.
Further configure the module at different levels
Modules may be able to be further configured at the virtual host, context, and script handler levels. More specific levels of configuration will always override more general levels. For example, virtual host-level configurations override server-level configurations and context-level configurations override virtual host-level configurations.