WebBuddhist Worker API

This is the worker backend API for the WebBuddhist application.

It handles background work such as TTS/audio generation and notification dispatch. Plan/content data owned by the main backend is accessed only via HTTP APIs — the worker does not share or query the backend Postgres schema for subtasks, plan days, or related domain tables.

Follow these steps to set up the project on your local machine:

1. Clone the repository:

   git clone https://github.com/yourusername/webuddhist-worker.git

2. Navigate to the project directory:

   cd webuddhist-worker

3. Install the dependencies:

   poetry install

Set at least:

The worker talks to the backend for audio job status, generation payloads (day/subtask content), and persisting generation results. Do not point DATABASE_URL at the backend database for plan/subtask data.

Start local infra from the backend repo if needed (Postgres/Mongo/Redis/etc.), then apply worker migrations against the worker database:

poetry run alembic upgrade head

These migrations cover worker tables (e.g. upcoming reminders), not backend plan tables.

1. Ensure the main backend is running (default http://127.0.0.1:8000).
2. Start the worker:

   poetry run uvicorn worker_api.app:api --port 8001 --reload

The application will be available at http://127.0.0.1:8001/.

You can access the Swagger UI for the API documentation at http://127.0.0.1:8001/docs.

To run tests, execute the following command:

poetry run pytest

To check the coverage:

poetry run pytest --cov=worker_api

poetry run coverage html

Open the coverage report:

open htmlcov/index.html

Alembic is used for handling worker-owned database migrations:

1. Create a new migration:

   poetry run alembic revision --autogenerate -m "description of migration"

2. Apply the latest migrations:

   poetry run alembic upgrade head

3. Downgrade to a previous migration:

   poetry run alembic downgrade -1

4. View the current migration history:

   poetry run alembic history

5. Show the current migration state:

   poetry run alembic current

This worker can reuse the same local Docker services as WeBuddhist-Backend (Postgres, MongoDB, Redis, Elasticsearch), but:

• Backend plan/content data is fetched and updated through backend internal APIs
• Worker Postgres should only hold worker-owned tables

Typical local ports:

• PostgreSQL: 5434
• MongoDB: 27017
• Redis/Dragonfly: 6379
• Elasticsearch: 9200

Both apps can run simultaneously:

• WeBuddhist-Backend: http://127.0.0.1:8000
• webuddhist-worker: http://127.0.0.1:8001