Welcome to a very small document! It is entirely on purpose. This document assumes you have already installed and enabled mod_lua. If you haven't done so yet, Click here to read about how you do that.
Setting up mod_lua doesn't require a whole lot of work, in fact it pretty much runs out of the box. If all you wish is to run .lua scripts as web applications, then you need only follow the steps outlined in the "Getting started with web apps" document and you're all set. If you are interested in working with hooks, follow the guide in "Getting started with hooks" document. For filters, check out the "Filters introduction".
You may want to check out the "Tweaking mod_lua" document to see how to increase the performance of mod_lua, as well as learn about some considerations to make when using mod_lua for hooks or web apps.
If all your scripts for hooks/filters are placed in the same folder - let's say /etc/lua/scripts -
then you can avoid having to type the full url every time you configure a hook/filter by using the
LuaScope directive. This directive sets the root path from which all LuaHook* directives
are evaluated. Consider the following:
LuaHookTranslateName /etc/lua/scripts/translate.lua translate_name LuaHookMapToStorage /etc/lua/scripts/mapper.lua map LuaOutputFilter ExampleFilter /etc/lua/scripts/filter.lua output_filter
With LuaRoot set, you can shorten these lines a bit:
LuaRoot /etc/lua/scripts/ LuaHookTranslateName translate.lua translate_name LuaHookMapToStorage mapper.lua map LuaOutputFilter ExampleFilter filter.lua output_filter