cache-handler VS lua-nginx-module

That's outdated information. The cache handler plugin is ready to use: https://github.com/caddyserver/cache-handler

In case you missed it: https://github.com/caddyserver/caddy/issues/2786

Those issues are a thing of the past. There's no use bringing it up again, tbh.

> like acting as a cache

That's fair, we have a WIP cache module here https://github.com/caddyserver/cache-handler, it should be ready soon!

All these have been written in the nginx configuration. Caddy is powerful and robust, but I'm not ready to rewrite all these into a Caddyfile. Moreover, a critical feature is missing in Caddy: there isn't a caching layer.

"small embeddable dynamic languages" are usually used to configure or program other larger compiled applications. This is bes understood by example:

https://create.roblox.com/docs/tutorials/scripting/basic-scr... - make a mini game in Roblox

https://github.com/openresty/lua-nginx-module?tab=readme-ov-... - configure and extend NGINX

https://wezfurlong.org/wezterm/config/lua/general.html - make your terminal more useful (my personal config changes the tab color based on the process name - https://github.com/bbkane/dotfiles/blob/master/wezterm/dot-c...

https://m.youtube.com/watch?v=MQBr9hwf0BY - configure your text editor

If your service is self-hosted, you can build the rate limit rules in Nginx using the OpenResty framework. Note that, if you are using OpenResty, you can use a shared dictionary and you don't necessarily need Redis. However, if you want to use redis though, then you need a redis client like the lua-resty-redis.

You may also wish to open a question on the OpenResty repo, as there are not many OpenResty folks that follow this subreddit.

/u/givmedat - Your best bet is to use njs module or the nginx lua module I think.

I drop logs at the first app LB using openresty's lua plugin for nginx. This goes into my data lake and we work on it from there. Does this work for everyone? No. Does it work for my F500 employer? Yes. Are there better ways to do this? Sorta.

# - https://github.com/openresty/lua-nginx-module/

We want the client to read the YAML file regularly. For this, we can leverage the power of the Lua Nginx module. It's part of OpenResty, which Apache APISIX is built upon. The module offers additional APIs, and two of them are particularly useful:

Depending on how complicated your Python logic is, one option is to use nginx+Lua (https://github.com/openresty/lua-nginx-module). Another option is to extend Envoy (https://www.envoyproxy.io/docs/envoy/latest/extending/extending).