Using the latest version of lua-resty-core with the current stable version (1.13.6.1)

kostya.y · 2018-02-02T01:35:02+00:00

Thank you very much!On Thursday, 1 February 2018 18:24:21 UTC-8, Igor Clark wrote:Yes that's right - this allows access:location = /access-test { ...

Using the latest version of lua-resty-core with the current stable version (1.13.6.1)

kostya.y

I was trying to get errlog.raw_log to work with my current openresty installation (1.13.6.1) and after spending countless hours trying to figure out why the raw_log function was undefined realized that the openresty bundle ships with an old lua-resty-core version.

I would like to use the new version, whats the best way to approach this? The is a warning on the lua-resty-core page saying: "This library is included with every OpenResty release. You should use the bundled version of this library in the particular OpenResty release you are using. Otherwise you may run into serious comaptibility issues.".

When is the new version going to be released? Can I create my own bundled version?

Thanks for the help.

thibaultcha

Hi,

The raw_log API is scheduled to be shipped with the next release (but is already in the master branch of lua-resty-core, hence why you are see it documented there).

You have more or less three options:

1. If you really know what you are doing, you _could_ get a local clone of lua-resty-core's master branch, and have it somewhere in your LUA_PATH (or lua_package_path) that takes precedence over the one shipped with your current release of OpenResty.

The current master of lua-resty-core requires ngx_lua 0.10.12+, but the latest OpenResty release ships with 0.10.11. So you would have to edit this line to ensure the module loads:

https://github.com/openresty/lua-resty-core/blob/master/lib/resty/core/base.lua#L21

Then, you'll want to inspect the list of changes between the two versions and make sure that none of them will affect the lua-resty-core API you are already using:

https://github.com/openresty/lua-nginx-module/compare/v0.10.11...v0.10.12rc2

There's quite a lot of them, I would be extra careful. Probably a bad idea.

2. Another option is to create your own OpenResty bundle from the mirror-tarballs script:

https://github.com/openresty/openresty/blob/master/util/mirror-tarballs

This is a saner alternative since it will bundle a compatible ngx_lua module with the latest lua-resty-core changes you want. However, you will be getting a work-in-progress release.

3. Finally, the third option would be to apply the raw_log patches from both the ngx_lua and lua-resty-core PRs and apply them yourself to OpenResty, before recompiling it. Probably the most conservative option of the three. To retrieve the raw patches, add '.patch' at the end of the URL, like so:

https://github.com/openresty/lua-resty-core/pull/128.patch

I hope you find the raw_log API useful.

Cheers,
Thibault

On 2/1/18 9:35 AM, Kostya Y wrote:

Hi
I was trying to get errlog.raw_log to work with my current openresty installation (1.13.6.1) and after spending countless hours trying to figure out why the raw_log function was undefined realized that the openresty bundle ships with an old lua-resty-core version.

I would like to use the new version, whats the best way to approach this? The is a warning on the lua-resty-core page saying: "This library is included with every OpenResty release. You should use the bundled version of this library in the particular OpenResty release you are using. Otherwise you may run into serious comaptibility issues.".

When is the new version going to be released? Can I create my own bundled version?

Thanks for the help.
.