How to compile module?

romadzao · 2016-05-21T08:01:26+00:00

You may also find this nginx module useful: https://github.com/GUI/nginx-upstream-dynamic-servers It primarily offers dynamic resolving of se...

How to compile module?

romadzao

I was confused that workers can't interact so I want to write a module. First I want to write integrated in ngx API helloworld. Is there any guide how to make module for openresty?

If I change something in /usr/local/openresty/lualib/resty/websocket/server.lua (for example), it will have effect.

But if I add function or remove all code from /usr/local/openresty/lualib/resty/core/worker.lua it has no effect, why?

Are core lua files precompiled somehow into nginx?

Have I compile all project each time when I changing module or there is easier way?

aapo.talvensaari

On Saturday, 21 May 2016 03:01:27 UTC+3, Romaboy wrote:

I was confused that workers can't interact so I want to write a module. First I want to write integrated in ngx API helloworld. Is there any guide how to make module for openresty?
If I change something in /usr/local/openresty/lualib/resty/websocket/server.lua (for example), it will have effect.
But if I add function or remove all code from /usr/local/openresty/lualib/resty/core/worker.lua it has no effect, why?
Are core lua files precompiled somehow into nginx?
Have I compile all project each time when I changing module or there is easier way?

Core is basically FFI version of PUC Lua interfaces. If you don't include resty.core, then you are using PUC Lua bindings.

romadzao

As I uderstood, that is that code: https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_worker.c

So lua files in core folder are unnecessary at all.

jenders

On Monday, May 23, 2016 at 6:29:13 AM UTC-7, Romaboy wrote:

As I uderstood, that is that code: https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_worker.c
So lua files in core folder are unnecessary at all.

Don't quote me but I think these are JIT compiled on first execution. Maybe you're looking for something like:

lua_code_cache off;

While testing?

aapo.talvensaari

On Monday, 23 May 2016 16:29:13 UTC+3, Romaboy wrote:

As I uderstood, that is that code: https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_worker.c
So lua files in core folder are unnecessary at all.

Okay, the long version then.

- Lua Nginx Module is C-code

- Lua Nginx Stream Module is C-code

Now there are two wayt to write bindings with LuaJIT (see _JIT_).

1. Normal stack based Lua C API (that usually needs a C-coded wrapper library)

2. LuaJIT FFI based API (that usually is plain Lua, but it may coma handy to provide a better suited C API for that)

Then let's look at OpenResty or Lua Nginx Module, it can be build with:

1. LuaJIT

2. PUC Lua

The first one is default. The second one cannot use LuaJIT FFI bindings.

By default there are PUC Lua bindings to those APIs that you said. Those are PUC Lua Bindings, but making this line in init_by_lua*:

require "resty.core"

You actually monkey patch the PUC Lua bindings and replace them with JITtable FFI bindings. That single line can provide you a nice performance boost. If you don't have that line, then you will be using PUC Lua bindings, and that will work too. Adding that line will only work with LuaJIT of course.

Some new features are probably only going to be supporting FFI, but the current ones are there for backward compatibility.

Does that explain you what is going on?

aapo.talvensaari

On Monday, 23 May 2016 20:44:21 UTC+3, Josh Enders wrote:

On Monday, May 23, 2016 at 6:29:13 AM UTC-7, Romaboy wrote:
As I uderstood, that is that code: https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_worker.c
So lua files in core folder are unnecessary at all.

Don't quote me but I think these are JIT compiled on first execution. Maybe you're looking for something like:

lua_code_cache off;

While testing?

Lua normally caches everything in package.loaded when you do require, e.g. local ws = require "resty.websocket.server" (it will never not be read again from the file, if you don't cleanup package.loaded or use that setting above.

agentzh

Hello!

On Fri, May 20, 2016 at 5:01 PM, Romaboy wrote:
> I was confused that workers can't interact so I want to write a module.

I'm not sure about this. What do you mean?

> First I want to write integrated in ngx API helloworld. Is there any guide
> how to make module for openresty?

What kind of modules are you talking about? Lua-level modules? NGINX
C-level modules that extend ngx_lua's Lua API?

> If I change something in
> /usr/local/openresty/lualib/resty/websocket/server.lua (for example), it
> will have effect.

Maybe you have forgot to reload your nginx?

> But if I add function or remove all code from
> /usr/local/openresty/lualib/resty/core/worker.lua it has no effect, why?

You need to reload your nginx when you change the code of already
loaded Lua modules.

> Are core lua files precompiled somehow into nginx?

Nope. Unless you explicitly configure it to:

    https://github.com/openresty/lua-nginx-module#statically-linking-pure-lua-modules

> Have I compile all project each time when I changing module or there is
> easier way?

For development, instead of reloading your nginx each time you make
changes to your Lua module files, you can turn off the lua_code_cache
directive in your nginx.conf.

Regards,
-agentzh