Skip to content

Add worker-monitor service to Docker Compose files #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Add worker-monitor service to Docker Compose files #127

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docker-compose-dev.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,17 @@ services:
- ${HOST_APP_PORT:-3000}:8080
environment:
<<: [*shared-env, *frontend-env]
worker-monitor:
container_name: marble-worker-monitor
image: ghcr.io/riverqueue/riverui:latest
ports:
- ${WORKER_MONITOR_PORT:-8081}:8080
environment:
DATABASE_URL: "postgresql://postgres:changeme@db:${PG_PORT:-5432}/marble"
RIVER_BASIC_AUTH_USER: ${RIVER_BASIC_AUTH_USER:-}
RIVER_BASIC_AUTH_PASS: ${RIVER_BASIC_AUTH_PASS:-}
depends_on:
- db
firebase_auth:
container_name: firebase-auth
image: europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest
Expand Down
11 changes: 11 additions & 0 deletions docker-compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,17 @@ services:
- ${HOST_APP_PORT:-3000}:${APP_PORT:-8080}
environment:
<<: [*shared-env, *frontend-env]
worker-monitor:
Copy link
Contributor

@Pascal-Delange Pascal-Delange Aug 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we should recommend installation of this tool in a prod environment. Do you see any security risks @apognu ?

container_name: marble-worker-monitor
image: ghcr.io/riverqueue/riverui:latest
ports:
- ${WORKER_MONITOR_PORT:-8081}:8080
environment:
DATABASE_URL: "postgresql://postgres:${PG_PASSWORD:-changeme}@db:${PG_PORT:-5432}/marble"
RIVER_BASIC_AUTH_USER: ${RIVER_BASIC_AUTH_USER:-}
Copy link
Contributor

@Pascal-Delange Pascal-Delange Aug 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we expose those configuration variables (also WORKER_MONITOR_PORT above), we should define and document them in the .env.example file. If I'm not getting this backwards (honestly it's tricky to remember), only env vars interpolated from the .env file are used in those ${ENV:-} blocks.

RIVER_BASIC_AUTH_PASS: ${RIVER_BASIC_AUTH_PASS:-}
depends_on:
- db

# NB: the docker compose file includes an elasticsearch image for the sake of completeness, but we strongly
# suggest using a production-grade instance to run Marble in a production environment
Expand Down