fix: install litestream in Dockerfile to prevent Railway deploy failure - #52
Merged
Merged
Conversation
PR #51 added a Dockerfile for Glama.ai MCP verification, but Railway used it to build production (despite railway.json pinning "builder": "NIXPACKS") and the deploy failed: Deploy > Create container The executable `/app/bin/litestream` could not be found. railway.json's deploy.startCommand always wraps uvicorn with litestream for continuous SQLite replication, regardless of which builder produced the image. Previously only nixpacks.toml's [phases.litestream] installed that binary. This Dockerfile now installs the identical binary (same version/URL as nixpacks.toml), so it is correct no matter which builder Railway picks. Production itself was not affected -- Railway kept serving the last successful deploy -- but every subsequent deploy would have failed the same way until this is merged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
PR #51 added a Dockerfile for Glama.ai MCP verification, but Railway used it to build production (despite railway.json pinning "builder": "NIXPACKS") and the deploy failed:
Deploy > Create container
The executable
/app/bin/litestreamcould not be found.railway.json's deploy.startCommand always wraps uvicorn with litestream for continuous SQLite replication, regardless of which builder produced the image. Previously only nixpacks.toml's [phases.litestream] installed that binary. This Dockerfile now installs the identical binary (same version/URL as nixpacks.toml), so it is correct no matter which builder Railway picks.
Production itself was not affected -- Railway kept serving the last successful deploy -- but every subsequent deploy would have failed the same way until this is merged.