openresty freebsd port (package)

danger · 2016-01-30T18:55:04+00:00

On Sun, Jan 31, 2016 at 3:20 PM, Lord Nynex <lord...@gmail.com> wrote:Hello,I would like to follow up on this issue. Can you please file an issue at&#x...

openresty freebsd port (package)

danger

Hello,

we would like to try the OpenResty project out. We use FreeBSD OS on our
servers and of course we also use FreeBSD ports to install 3rd party
packages. I understand that openresty works on FreeBSD platform. I have
checked out the project web site and from my understanding it looks to
me like the openresty project is just a bundle of a several nginx modules.

Furthermore, it looks like a few of the openresty bundled modules are
already included in the nginx port[1], e.g. echo, headers_more, drizzle,
to name a few.

So I am wondering if openresty adds any patches to nginx that we would
need to apply to have it complete, or is it really just an upstream
nginx with the modules listed at http://openresty.org/#Components?
Because in such case it does not make sense to make a separate openresty
port and only add the missing modules to the nginx port.

Thanks!

[1]
https://svnweb.freebsd.org/ports/head/www/nginx-devel/Makefile?revision=407510&view=co

lordnynex

Hello,

You are correct that OpenResty bundles nginx modules rather than forks it. The FreeBSD support is primarily from nginx's support of kqueue.

To answer your question simply; yes, OpenResty does apply patches to Nginx at compile time. It also bundles some optional patches for development purposes. Please see https://github.com/openresty/openresty/tree/master/patches exact details.

I am not familiar with FreeBSD so I'm unclear about where these module sources are being pulled from. It's important to understand that some openresty modules are forked or completely rewritten from other legacy 3rd party modules of similar name. Please see https://www.nginx.com/resources/wiki/modules/ for a more detailed view of the different modules. Here you can see the name overlap in some modules. On a sidenote, this is a somewhat common phenomenon in nginx module development. In many cases, people write excellent modules to suit their immediate needs and, for whatever reason, decide not to continue development. A good example of this is looking at the forks of the RTMP module.

OpenResty largely revolves around lua-nginx-module (https://github.com/openresty/lua-nginx-module) and many other modules rely on it. For example, agentzh has carefully thought out the internal API's and designed them for performance and efficiency. The shared dict interface is a noteworthy reference. OpenResty's remarkable performance draws on this dogfooding approach. (There is a very modest line about modules 'playing well with one another' at http://openresty.org/#About)

In this situation it seems relatively easy to accidentally compile nginx with the 'wrong' 3rd party module. In such case, you can not expect the same stability from some or all openresty features. Without testing, I would say the features, functionality and outcome would be unpredictable. Please note, looking at https://svnweb.freebsd.org/ports/head/www/nginx/files/ I notice there are several possible patches for 3rd party modules that are no longer maintained. I am not sure what stability implications this creates, so you should pull in 3rd party modules cautiously.

If there is a separate OpenResty port, I highly recommend you use it. OpenResty follows nginx and luajit development very closely. In many cases it's modules development is actually sponsored by Cloudflare and will continue to receive enhancements and bug fixes far into the foreseeable future. An example of this is http://openresty.org/#ChangeLog1009007, where a new build was published in parallel with the official nginx release.

I do not personally have much visibility into FreeBSD, but I can say there are several companies using OpenResty in their (Free|Open)BSD appliances. Please keep us informed of any issues you encounter along the way.

On Sat, Jan 30, 2016 at 2:54 AM, Daniel Gerzo <da...@freebsd.org> wrote:

Hello,

we would like to try the OpenResty project out. We use FreeBSD OS on our
servers and of course we also use FreeBSD ports to install 3rd party
packages. I understand that openresty works on FreeBSD platform. I have
checked out the project web site and from my understanding it looks to
me like the openresty project is just a bundle of a several nginx modules.

Furthermore, it looks like a few of the openresty bundled modules are
already included in the nginx port[1], e.g. echo, headers_more, drizzle,
to name a few.

So I am wondering if openresty adds any patches to nginx that we would
need to apply to have it complete, or is it really just an upstream
nginx with the modules listed at http://openresty.org/#Components?
Because in such case it does not make sense to make a separate openresty
port and only add the missing modules to the nginx port.

Thanks!

[1]
https://svnweb.freebsd.org/ports/head/www/nginx-devel/Makefile?revision=407510&view=co
.