wip
This commit is contained in:
@@ -34,7 +34,7 @@ The `rhai_worker` crate implements a standalone worker service that listens for
|
||||
/path/to/worker --redis-url redis://127.0.0.1/ --circle-public-key 02...abc
|
||||
```
|
||||
2. The `run_worker_loop` connects to Redis and starts listening to its designated task queue (e.g., `rhai_tasks:02...abc`).
|
||||
3. A `rhai_dispatcher` submits a task by pushing a `task_id` to this queue and storing the script and other details in a Redis hash.
|
||||
3. A `rhai_supervisor` submits a task by pushing a `task_id` to this queue and storing the script and other details in a Redis hash.
|
||||
4. The worker's `BLPOP` command picks up the `task_id`.
|
||||
5. The worker retrieves the script from the corresponding `rhai_task_details:<task_id>` hash.
|
||||
6. It updates the task's status to "processing".
|
||||
@@ -46,7 +46,7 @@ The `rhai_worker` crate implements a standalone worker service that listens for
|
||||
|
||||
- A running Redis instance accessible by the worker.
|
||||
- An orchestrator process (like `launcher`) to spawn the worker.
|
||||
- A `rhai_dispatcher` (or another system) to populate the Redis queues.
|
||||
- A `rhai_supervisor` (or another system) to populate the Redis queues.
|
||||
|
||||
## Building and Running
|
||||
|
||||
|
Reference in New Issue
Block a user