openresty / openresty/lua-resty-websocket
use websocket client to sync data in local redis before nginx is accessible
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 523
- Forks
- 112
- Avg merge
- 1d 16m
- Merged PRs (30d)
- 2
Description
Hello,
Im not sure if that's possible but before I look at openresty / LUA scripting, within my microservice (nodejs), I had a websocket client that was connecting to a remote server to sync up data into redis before the service was accessible.
Those data are relative to the authentication of the users, routes, certificates and should be available before the service is up.
Can I do the same thing directly on nginx level using LUA ( and lua-resty-weboscket / lua-resty-redis ) ? As websocket and redis are not usuable in the init_* block, Im wondering how I could proceed.
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the OpenResty init_* block behavior and the lua-resty-websocket and lua-resty-redis entry points mentioned in the issue. Determine whether the requested pre-start synchronization can be supported at the nginx level, and document a confirmed approach or the limitation that prevents it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx, node.js, redis
- Domain
- backend, databases, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100