zeekayandHanzo Dev
31977edc07
recipe_test.go is package main at the repo root and calls Detect, fileset and Plan.Recipe. None of those exist in the tree, and it imports moby/docker-image-spec, which go.sum no longer carries, so go vet ./... stops at the root package before it type-checks anything: recipe_test.go:10:2: missing go.sum entry for module providing package github.com/moby/docker-image-spec/specs-go/v1 Without the file the root is not a package and go vet ./... is clean. Co-authored-by: Hanzo Dev <[email protected]>
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.