From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] lua-resty-http: new package
Date: Fri, 05 May 2017 12:29:14 +0200 [thread overview]
Message-ID: <87pofntx51.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1493935354.76899857@f13.my.com> (semenak's message of "Fri, 05 May 2017 01:02:34 +0300")
>>>>> "semenak94" == semenak94 <semenak94@mail.ru> writes:
> Hello,
> Well, I'm also very far from nginx expert, but yes, it
> lua-nginx-module, which we need in our special embedded linux. So, if
> you don't explicitly have nginx modules in buildroot, how should we
> deal with it?
So how are you using it now?
We currently don't have any explicit handling of the nginx-lua
module. You could conceptually do something with the 'nginx additional
modules' (BR2_PACKAGE_NGINX_ADD_MODULES) option, but there's no
guarantee that nginx builds after luajit.
I guess the proper solution would be to add an explicit nginx-lua
module, similar to what we already have for nginx-dav-ext / nginx-naxsi
/ nginx-upload.
Samuel and Adam, you have added / been active around nginx and modules,
any input?
>> ?> +config BR2_PACKAGE_LUA_RESTY_HTTP
>> ?> + bool "lua-resty-http"
>> ?> + help
>> ?> + ? Lua HTTP client cosocket driver for OpenResty / ngx_lua.
>> ?> +
>> ?> + ? http://github.com/pintsized/lua-resty-http
>> Sorry for the slow response, but this patch apparently never made it to
>> my mailbox? (It is in the archive, so it must have been an issue on my
>> side).
>> I'm far from an expert in nginx, but isn't this an extension to the
>> lua-nginx-module that we don't (explicitly) have in Buildroot? Is it in
>> any way useful without it?
>> What is your use case for it?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-05-05 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 22:02 [Buildroot] [git commit] lua-resty-http: new package semenak94 at mail.ru
2017-05-05 10:29 ` Peter Korsgaard [this message]
2017-05-05 13:59 ` Danomi Manchego
2017-05-05 14:34 ` Peter Korsgaard
2017-05-05 21:16 ` Danomi Manchego
-- strict thread matches above, loose matches on Subject: below --
2017-05-04 20:23 Thomas Petazzoni
2017-05-04 21:02 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pofntx51.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox