2
Nginx Development Kit (NDK)
3
===========================
7
The NDK is an Nginx module that is designed to extend the core functionality of the
8
excellent Nginx webserver in a way that can be used as a basis of other Nginx modules.
10
It has functions and macros to deal with generic tasks that don't currently have
11
generic code as part of the core distribution. The NDK itself adds few features
12
that are seen from a user's point of view - it's just designed to help reduce the
13
code that Nginx module developers need to write.
15
Nginx module developers wishing to use any of the features in the NDK should specify
16
that the NDK is a dependency of their module, and that users will need to compile
17
it as well when they compile their own modules. They will also need to declare in
18
their own modules which features of the NDK they wish to use (explained below).
20
If you are not an Nginx module developer, then the only useful part of this project
21
will be the 'usage for users' section below.
26
The NDK is now considered to be stable. It is already being used in quite a few third
32
- additional conf_set functions for regexes, complex/script values, paths...
33
- macros to simplify tasks like checking for NULL values when doing ngx_array_push
34
- patches to the main source code
35
- ngx_auto_lib_core generic external library handler is included (see separate readme)
43
The kit itself is designed in a modular way, so that only the required code is compiled.
44
It's possible to add just a single NDK module, a few or all of them.
46
auto-generated & easily extensible :
48
Many of the macros available in the NDK are auto-generated from simple configuration
49
files. This makes creating similar macros for your own code very simple - it's usually
50
just the case of adding an extra line to a config file and re-running the build script.
55
If another Nginx module you wish to use specifies that the NDK is a dependency, you
56
will need to do the following :
58
1 - download the source (http://github.com/simpl-it/ngx_devel_kit)
60
2 - unpack the source (tar -xzf $name)
62
3 - compile Nginx with the following extra option
64
--add-module=/path/to/src
68
./configure --add-module=/path/to/ndk/base --add-module=/path/to/another/mod
73
To use the NDK in your own module, you need to add the following :
75
1 - add this line to your module
79
note : since the NDK includes the following lines
81
#include <ngx_config.h>
85
you can replace these with the single include above.
87
2 - add the following line in the config file for your module :
89
have=NDK_[module_name] . auto/have
91
for each NDK module that you wish to use (you need to include auto/have multiple
92
times if you wish to use multiple NDK modules.
95
Note : the old method of setting
97
CFLAGS="$CFLAGS -DNDK_[module_name]"
99
is now deprecated. It will still work, but results in unnecessary lines being
100
displayed when compiling Nginx.
103
Warning : using NDK_ALL
105
You can also set NDK_ALL to include all the NDK modules. This is primarily as
106
a convenience in the early stages of development of another module. However,
108
DO NOT LEAVE 'NDK_ALL' IN YOUR CONFIG FILE WHEN PUBLISHING
110
Although the NDK is fairly small now, it could in time become a large repository
111
of code that would, if using NDK_ALL, result in considerably more code being compiled
117
- documentation for modules that don't already have it
118
- additional phase-handler functions
119
- generically testing for needing to add a handler
120
- remove dependency of set_var on OpenSSL being compiled in
128
Contributing / Feedback
130
If you are an Nginx module developer, and have developed some functions that are
131
generic in nature (or would be easily adapted to be so), then please send them to
132
me at the address below, and I'll add them to the kit.
137
Marcus Clyne (contact at simpl dot it)