fix: remove root Dockerfile -- restore Railway to Nixpacks (productio… - #53
Merged
Merged
Conversation
…n outage) URGENT: api.xfinlab.com has been returning 502 on every request (real user traffic and the MCP endpoint alike) since PR #51 added a root Dockerfile for Glama.ai's MCP listing verification. PR #52 fixed the missing-litestream build failure, but the deploy still never actually serves traffic afterward: "Completed" status, but 0% CPU/memory for a sustained window, deploy logs go silent right after litestream restore finishes its last WAL entry, and every live request times out at Railway's 15s gateway limit with a 502. railway.json explicitly pins "builder": "NIXPACKS", but the mere presence of a root Dockerfile appears to make Railway build with it instead -- the same behavior that caused PR #51's original failure. Whatever additional difference exists between the Docker-built image and the previously-working Nixpacks-built image (permissions, base image, etc.) leaves the app unable to ever start serving, with no error logged. Removing the Dockerfile is safe: Glama's own "Server" build flow never actually reads this file (it clones the repo and generates its own Dockerfile from a template internally, confirmed by inspection). The XFINLAB MCP listing on Glama was instead submitted via their "Connector" flow (a plain HTTPS URL, glama.ai/mcp/servers -- Connectors -- XFINLAB Intelligence), which needs no Dockerfile at all. The originating requirement (punkpeye/awesome-mcp-servers PR #13369) is also now closed. This restores the exact build path (nixpacks.toml) that was working correctly before 2026-09-09.
|
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.
…n outage)
URGENT: api.xfinlab.com has been returning 502 on every request (real user traffic and the MCP endpoint alike) since PR #51 added a root Dockerfile for Glama.ai's MCP listing verification. PR #52 fixed the missing-litestream build failure, but the deploy still never actually serves traffic afterward: "Completed" status, but 0% CPU/memory for a sustained window, deploy logs go silent right after litestream restore finishes its last WAL entry, and every live request times out at Railway's 15s gateway limit with a 502.
railway.json explicitly pins "builder": "NIXPACKS", but the mere presence of a root Dockerfile appears to make Railway build with it instead -- the same behavior that caused PR #51's original failure. Whatever additional difference exists between the Docker-built image and the previously-working Nixpacks-built image (permissions, base image, etc.) leaves the app unable to ever start serving, with no error logged.
Removing the Dockerfile is safe: Glama's own "Server" build flow never actually reads this file (it clones the repo and generates its own Dockerfile from a template internally, confirmed by inspection). The XFINLAB MCP listing on Glama was instead submitted via their "Connector" flow (a plain HTTPS URL, glama.ai/mcp/servers -- Connectors -- XFINLAB Intelligence), which needs no Dockerfile at all. The originating requirement (punkpeye/awesome-mcp-servers PR #13369) is also now closed.
This restores the exact build path (nixpacks.toml) that was working correctly before 2026-09-09.