Skip to content

fix: restore Railway server container builds - #1279

Draft
lalalune wants to merge 2 commits into
mainfrom
codex/railway-container-repair
Draft

lalalune wants to merge 2 commits into
mainfrom
codex/railway-container-repair

Conversation

@lalalune

@lalalune lalalune commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

Railway cannot build the server because the pinned Bun image uses Debian Bullseye repositories whose package downloads now return 404. Use Node 22 on Bookworm for the builder and copy the existing pinned Bun binary into it. Also create the actual @hyperforge workspace directory used by runtime links.

Run the standalone Docker build on pull requests so deployment recipe failures are caught before merging. The Dockerfile performs its own install/build; existing lint, test, and application build gates remain unchanged.

Validation:

  • git diff --check passed.
  • Railway reproduced the original Bullseye package-download failure at commit b67375d.
  • The repaired builder passed Debian package installation on Railway at 376b6e8. The rollout was then cancelled before runtime activation.
  • Full Docker CI validation is running at b68fbe3.

Production activation remains blocked by an empty DATABASE_URL with local PostgreSQL disabled. The service also enables automatic betting and market-making; an operator must handle those features before activation. No production secrets or feature flags were changed.

This branch has not been deployed

No deployments
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