Michael BiancoandGitHub
e26e0a76cf
* feat(mise): configure railpack to use musl-compatible mise binary - Add dependencies (bash, git) required by mise's internal logic. - Pin the mise version to match the repository's configuration. - Symlink the installed musl-compatible mise binary to the railpack cache directory to ensure binary compatibility on the host side. Generated-by: aiautocommit * feat(mise): target musl-based builds for linux - Refactor getAssetName to accept platform parameters, improving testability. - Update linux asset resolution to favor musl-based binaries for improved compatibility with alpine and other musl environments. - Add unit tests for platform-specific asset naming and error handling. Generated-by: aiautocommit
Railpack
Railpack is a tool for building images from source code with minimal configuration. It is the successor to Nixpacks and incorporates many of the learnings from running Nixpacks in production at Railway for several years.
Getting Started
# Install mise & railpack
curl -sSL https://mise.run | sh
mise install github:railwayapp/railpack@latest
# start BuildKit container & let railpack know about it
docker run --rm --privileged -d --name buildkit moby/buildkit
export BUILDKIT_HOST='docker-container://buildkit'
# create a Next.js app
npm create next-app@latest my-app
cd my-app
# build and run the app!
railpack build .
docker run -p 3000:3000 -it my-app
Railpack automatically detects the project type (Next.js, in this case, but many languages & frameworks are supported!) and generates an optimized container image.
Note: The above steps are for running Railpack locally to experiment and test. If you deploy on Railway, Railpack runs automatically when you push changes to your repository.
Documentation
Full documentation for both operators (platforms, like Railway) and users (developers using Railpack to build their applications) is available at railpack.com.
Contributing
Railpack is open source and open to contributions. See the CONTRIBUTING.md file for more information.