sailfork / t3code-github / .repos/ alchemy-effect/ examples/ railway-website-nextjs
- app
- public
- test
- .gitignore
- alchemy.run.ts
- next.config.mjs
- package.json
- postcss.config.mjs
- README.md
- tsconfig.json
- tsconfig.next.json
.repos/alchemy-effect/examples/railway-website-nextjs/README.md
Railway Website: Next.js
Deploys a Next.js site to Railway with
Railway.Website.Nextjs — no adapter setup in the project config.
Alchemy generates a Dockerfile and uploads the build context; Railway builds the image. The Service listens on port 3000.
app/page.jsxis server-rendered on the Railway Service and readsGREETINGfromprocess.env.app/api/hello/route.tsis an App Router API route.- This is
next buildplus a long-running Node process — not OpenNext.
const site = yield* Railway.Website.Nextjs("Nextjs", {
env: { GREETING: "Hello from Next.js on Railway!" },
}); The integration package must be installed in the project (it is loaded dynamically at deploy time):
bun add -d @alchemy.run/frontend-frameworks Deploy
bun run deploy Unchanged sources skip the build entirely on subsequent deploys — the
input files are content-hashed (scoped by memo.include).
Dev
bun run dev alchemy dev runs the framework's own dev server (HMR included) and
no cloud resources are created.
Destroy
bun run destroy