Skip to content

Containerize the relay runtime - #232

Open
ariobarin wants to merge 1 commit into
mainfrom
chore/containerize-relay
Open

Containerize the relay runtime#232
ariobarin wants to merge 1 commit into
mainfrom
chore/containerize-relay

Conversation

@ariobarin

@ariobarin ariobarin commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Summary

  • add a multi-stage Node 24 relay image that runs as the non-root node user
  • extend Compose to run the relay with Postgres on loopback-only host ports
  • smoke-test the built container in Linux CI and document the Docker self-hosting path

Production Heroku remains on its supported Node buildpack deployment in this PR. This adds and validates the container artifact without coupling it to a production stack migration.

Validation

  • npm run check
  • docker build --progress=plain -t glossa-relay-pr1 .
  • docker compose -p glossa-pr1 up -d --build --wait
  • GET http://127.0.0.1:39100/healthz

@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
glossa Ignored Ignored Preview Aug 19, 2026 2:58pm

Request Review

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@ariobarin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a43c45ae-3659-4b67-9266-74123a656153

📥 Commits

Reviewing files that changed from the base of the PR and between 0958189 and 6e43718.

📒 Files selected for processing (5)
  • .dockerignore
  • .github/workflows/ci.yml
  • Dockerfile
  • compose.yaml
  • docs/self-hosting.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant