Multiple Sites with Different Configurations

aapo.talvensaari · 2014-03-06T05:39:31+00:00

Hello! On Wed, Mar 5, 2014 at 4:16 AM, santi kumar wrote: > ./sample-bt-off-cpu -p 11333 -t 5 > semantic error: while resolving probe point: identifi...

Multiple Sites with Different Configurations

aapo.talvensaari

Let's say I have multiple sites on single OpenResty server. Can I have say different package.path, and package.cpath for each server block in nginx config, or even location block? This same question extends to Lua too. For example with my lua-resty-template I would like to have a different template finder function or template base path configuration for each server block (maybe different package.path, and package.cpath too). How should I approach this?

As I understand each worker has it's own Lua, and that seems to indicate that configs are worker based (https://github.com/chaoslawful/lua-nginx-module#data-sharing-within-an-nginx-worker). I may have understood this wrong. One option could be ngx.ctx, and ngx.var is another. I could possibly use "set $root /some-dir/;" and then "ngx.var.root" in code in lua-resty-template - Can I directly read values of nginx configuration directives from Lua (i.e. root directive without setting $root var, is it ngx.var.document_root)? Also with ngx.var I cannot cache the value on Lua module level, as it is shared on different sites (and it is also discouraged to read it repeatable).

Could you point me to right direction?

After writing this I found this:

http://openresty.org/download/agentzh-nginx-tutorials-en.html

Haha, that's more than enough for explanations :-). But if you still have something to say to point me directly to right thing, that could help.

Kind Regards

Aapo

agentzh

Hello!

On Wed, Mar 5, 2014 at 1:39 PM, Aapo Talvensaari wrote:
> Let's say I have multiple sites on single OpenResty server. Can I have say
> different package.path, and package.cpath for each server block in nginx
> config, or even location block?

As long as you don't want separate output filters (like
header_filter_by_lua), then you can use multiple http {} blocks each
with its own virtual server defined by server {}. That way, each http
{} has its own standalone Lua VM instance.

NGINX's output filters are always global, alas.

> This same question extends to Lua too.

You need separate Lua VMs (note, not just separate Lua threads).

Best regards,
-agentzh

agentzh

Hello!

On Wed, Mar 5, 2014 at 1:39 PM, Aapo Talvensaari wrote:
> One option could be ngx.ctx, and ngx.var
> is another.

Both of these are per-request. They cannot go across the (sub)request boundary.

> I could possibly use "set $root /some-dir/;" and then
> "ngx.var.root" in code in lua-resty-template - Can I directly read values of
> nginx configuration directives from Lua (i.e. root directive without setting
> $root var, is it ngx.var.document_root)?

Yes, as long as the NGINX variables already exist. NGINX variables are
always created at configuration loading time. One cannot create new
NGINX variables at request time.

NGINX variables are expensive, both reading and writing. They are just
for inter-module communication. Be careful when use them in tight Lua
loops.

Regards,
-agentzh