build: drop nixpacks.toml so Railway keeps using Railpack - #3
Merged
Conversation
Adding railpack.json alongside the existing nixpacks.toml with a [phases.install] block caused Railway to switch builder from RAILPACK to NIXPACKS, and the nixpacks-generated install command failed with "cd: bot: No such file or directory". The previous production deploys all used the RAILPACK builder successfully; the install command was auto-detected from package.json. Removes nixpacks.toml entirely so Railway consistently selects RAILPACK, honours the Chromium apt-package list in railpack.json, and lets its Node.js provider auto-detect the install steps.
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.
Follow-up to PR #2. Adding railpack.json alongside the existing nixpacks.toml caused Railway to switch builder to NIXPACKS, and the resulting install command failed with 'cd: bot: No such file or directory'. Deleting nixpacks.toml lets Railpack stay in charge (matching how our sibling PK bot is configured) and picks up the apt-package list for Chromium.