PR-B4: wire interaction-worker into docker-compose - #32
Merged
Conversation
Adds the interaction-worker service, mirroring the established security-audit-worker/billing-worker precedent in this file exactly (build: Dockerfile.worker, restart: on-failure, depends_on mysql/redis service_healthy) -- no ghcr.io image published for it today, same gap those two services' own PR-B0/billing reports already flagged. Reuses auth-service's own DB_*/REDIS_URL values verbatim: the worker writes to the same `omnibioai` database auth-service itself uses (the `interactions` table PR-B2 created there), not a separate database. See omnibioai-auth's feature/pr-b4-interaction-consumer branch for the worker implementation this wires up.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Companion to omnibioai-auth#38.
Adds the
interaction-workerservice todocker-compose.yml, mirroringthe established
security-audit-worker/billing-workerprecedent inthis same file exactly (
build:from source +Dockerfile.worker,restart: on-failure,depends_onmysql/redisservice_healthy).Scope
Reuses
auth-service's ownDB_*/REDIS_URLvalues verbatim -- theworker writes to the same
omnibioaidatabaseauth-serviceitselfuses (the
interactionstable PR-B2 created there), not a separatedatabase. No
ghcr.ioimage is published for it today (same gapsecurity-audit-worker's own PR-B0 report andbilling-workeralreadyflagged for themselves).
Validated locally:
docker compose configparses the new servicecorrectly,
docker compose build interaction-workersucceeds, and thebuilt image was run end-to-end against isolated ephemeral Redis/MySQL
containers (never this repo's own shared dev stack) -- see
omnibioai-auth#38's own report for the full real-infra validation.
🤖 Generated with Claude Code