Hello!
On Thu, Aug 30, 2012 at 8:25 PM, Maanas wrote:
>
> 3. One thing is to prevent twisted and lengthy nginx.conf files.
> I do not understand this completely. I m sure debugging a ngnix.conf file
> would be complex as the application grows especially with not much
> understanding of the nginx internals.
>
> What i m working on is to split each group of end points into separate conf
> file and include. That way each conf file will be like one mini script for
> lua. Further, i m also thinking go use location { internal } to map common
> used functions / objects and lua to incapsulate the business logic. And then
> used sub request to actually process them. Further, this will also cache all
> the lua into ngnix. Yes i plan to use drizzle + rds_json. I saw the
> performance bench mark in one of your presentation. The idea of putting all
> this in intermal end point is to encapsulate the business logic. Do you see
> any problem with this approach.
>
I was not saying that pure nginx.conf scripting is bad. If you're
familiar with all the gotchas of nginx.conf scripting and can handle
all the pitfalls there, then it is totally fine ;)
I was just suggesting you should switch to Lua as soon as possible if
your nginx.conf becomes twisty and hard to maintain ;)
Best regards,
-agentzh
