Fix task module examples to working one (#62)

Author: CCXLV

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/logo_full.png" alt="FluxQueue" />
+  <img src="https://fluxqueue.ccxlv.dev/images/logo_full.png" alt="FluxQueue" />
 </p>
 
 <div align="center">

docs/tutorial/defininig_and_exposing_tasks.md

@@ -77,10 +77,10 @@ This pattern:
 When starting the worker, point it to your tasks module:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue default
+fluxqueue start --tasks-module-path myapp/tasks --queue default
 ```
 
-The worker will import `myapp.tasks` and discover all task functions that are exposed in the module.
+The worker will import `myapp/tasks` and discover all task functions that are exposed in the module.
 
 ## How It Works
 
@@ -145,13 +145,13 @@ __all__ = [
 In your first terminal:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue default
+fluxqueue start --tasks-module-path myapp/tasks --queue default
 ```
 
 In a second terminal:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue urgent
+fluxqueue start --tasks-module-path myapp/tasks --queue urgent
 ```
 
 ## Alternative: Single File

docs/tutorial/quickstart.md

@@ -67,10 +67,10 @@ def important_task(data: str):
 To process tasks, you need to run a worker. Make sure Redis is running, then start the worker:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue default
+fluxqueue start --tasks-module-path myapp/tasks --queue default
 ```
 
-The `--tasks-module-path` tells the worker where to find your task functions. It should be the module path where your tasks are defined (e.g., `myapp.tasks` if your tasks are in `myapp/tasks.py`). For more details, see [Defining and Exposing Tasks](defininig_and_exposing_tasks.md).
+The `--tasks-module-path` tells the worker where to find your task functions. It should be the module path where your tasks are defined (e.g., `myapp/tasks` if your tasks are in `myapp/tasks.py`). For more details, see [Defining and Exposing Tasks](defininig_and_exposing_tasks.md).
 
 ## Complete Example
 

docs/tutorial/worker.md

@@ -27,7 +27,7 @@ The worker is a standalone Rust-powered process (invoked through the `fluxqueue`
 !!! tip
     In development, you will usually run the worker through the dedicated Python CLI (`fluxqueue-cli`), which exposes a Python-friendly interface:
     ```bash
-    fluxqueue start --tasks-module-path myapp.tasks --queue default
+    fluxqueue start --tasks-module-path myapp/tasks --queue default
     ```
 
     For production, the recommended way is to run the underlying Rust binary `fluxqueue-worker` directly with the same flags. The `fluxqueue` CLI is there to make local development and experimentation nicer.
@@ -39,18 +39,18 @@ The worker is a standalone Rust-powered process (invoked through the `fluxqueue`
 Basic usage:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue default
+fluxqueue start --tasks-module-path myapp/tasks --queue default
 ```
 
 The worker runs in the **foreground**.  
 If you want multiple workers (for different queues or higher throughput), run each one in its **own terminal**:
 
 ```bash
 # Terminal 1 – default queue
-fluxqueue start --tasks-module-path myapp.tasks --queue default
+fluxqueue start --tasks-module-path myapp/tasks --queue default
 
 # Terminal 2 – urgent queue
-fluxqueue start --tasks-module-path myapp.tasks --queue urgent
+fluxqueue start --tasks-module-path myapp/tasks --queue urgent
 ```
 
 Press `Ctrl+C` in a worker terminal to trigger **graceful shutdown** (it finishes current work and cleans up executor metadata in Redis).
@@ -95,7 +95,7 @@ Example:
 ```bash
 fluxqueue start \
   --redis-url redis://localhost:6379 \
-  --tasks-module-path myapp.tasks \
+  --tasks-module-path myapp/tasks \
   --queue default
 ```
 
@@ -108,7 +108,7 @@ fluxqueue start \
 
 This should be the **module path**, not a file path:
 
-- `myapp.tasks` → imports `myapp/tasks/__init__.py`
+- `myapp/tasks` → imports `myapp/tasks/__init__.py`
 - `tasks` → imports `tasks.py`
 
 The worker imports that module and inspects it to find callables that have a `task_name` and `queue` attribute (these are normally added by the `@fluxqueue.task()` decorator).  
@@ -130,7 +130,7 @@ Use different queues to separate workloads:
 Example:
 
 ```bash
-fluxqueue start --tasks-module-path myapp.tasks --queue urgent
+fluxqueue start --tasks-module-path myapp/tasks --queue urgent
 ```
 
 ### `--save-dead-tasks`
@@ -259,11 +259,11 @@ Example (two workers for `default`, one for `urgent`):
 
 ```bash
 # Machine 1
-fluxqueue start --tasks-module-path myapp.tasks --queue default --concurrency 4
+fluxqueue start --tasks-module-path myapp/tasks --queue default --concurrency 4
 
 # Machine 2
-fluxqueue start --tasks-module-path myapp.tasks --queue default --concurrency 4
-fluxqueue start --tasks-module-path myapp.tasks --queue urgent --concurrency 2
+fluxqueue start --tasks-module-path myapp/tasks --queue default --concurrency 4
+fluxqueue start --tasks-module-path myapp/tasks --queue urgent --concurrency 2
 ```
 
 ---