Can only use one set of ledge options per request? about ledge

[pintsized]

Currently (because we haven't refactored yet based on the outcome of discussions on #11), this isn't possible. But with the suggested mechanism in #11, all options will actually be stored within the ngx.ctx table. This means that they are relevant to the current request only, and this is also true of sub-requests.. which have their own ngx.ctx space.

So in principle, when the new config mechanism is working (soon!), you can have different origin_location or redis_host options for requests and sub-requests.

Does that sound like what you need?

[bakins]

For now, yes. I'd like to help out if I can.

[pintsized]

Cool, nice one. I'm in the middle of working on refactoring the config stuff, so I'll get something committed soon.. feedback will be most welcome :)

In general, this whole project is in flux right now, as you will have gathered, but it's starting to make some sense. Do feel free to send pull requests and generally request / discuss features on here. Hopefully it'll be a little less fragile in the coming weeks..

[pintsized]

I've just committed a first pass of this.. So you can now do something like:

http {
    init_by_lua '
        rack = require "resty.rack"
        ledge = require "ledge.ledge"
        ledge.gset("origin_location", "/__ledge/example.com")
        ledge.gset("redis_host", 192.168.1.234)
    ';

    server {
        location / {
            content_by_lua '
                rack.use(ledge)
                rack.run()
            ';
        }
    }
}

[pintsized]

I should add that ledge.gset("cache_key_spec", table) isn't supported. Need to think about that a bit.

[pintsized]

I've sent a pull request to lua-nginx-module which adds ngx.get_phase() to the API. When this is released, we'll drop ledge.gset(). So config parameters can be set either globally during init_by_lua or per-location, both using the uniform ledge.set().