py-worker features
Generated from templates/py-worker/template.json. Features that remove Python
packages list their requirements.txt entries under “Packages”.
| Feature | Default | What it adds |
|---|---|---|
queueBullMQ consumers | Always | Workers pulling from the same Redis queues your Node API produces to, with graceful SIGINT/SIGTERM shutdown. |
loggingStructured logging | Always | |
databaseSQLAlchemy over Postgres | On | Direct database access to the same schema your API owns. Models are hand-written here rather than generated, so they must be kept in step with the Prisma schema by hand. Files it owns (2)
|
dockerDocker image | On | Files it owns (2)
|
ciForgejo Actions CI | On | Files it owns (1)
|
telemetryOpenTelemetry → OpenObserve | On | Traces, logs and metrics over OTLP (set OPENOBSERVE_URL/ORG/TOKEN, or any OTEL_* backend), with a span per job and Redis instrumentation. Off at runtime until connected. Files it owns (1)
|
temporalTemporal worker | Opt-in | Runs durable workflows and activities from temporal/ (an example of each included) on its own TEMPORAL_TASK_QUEUE, next to the BullMQ consumers, with a span per workflow and activity when telemetry is on. Pair with the API's temporal feature, which starts them. Files it owns (2)
|
temporalworks on the default Python image; its wheels include musl and glibc builds.telemetryoff removes every OpenTelemetry package; the job wrapper andsetup_telemetry()calls go with it.