migrate-to-railcode
Installation
SKILL.md
Migrate to Railcode
A migration is a port, not a rewrite: the project already works somewhere, and the job is to keep what it does for its users while replacing what the old host provided (auth, a database, env vars, cron, file storage) with what Railcode provides.
Most internal tools fit. Usually one or two pieces have no direct equivalent, and almost all of those can be rebuilt a different way that the user will not notice — see Find another way. A short list of things cannot be hosted at all today — see What Railcode cannot host today. Know both lists before you promise anything.
Guides by source project:
| Source project | Guide | Status |
|---|---|---|
| Next.js (App Router) | references/nextjs.md | Supported as "type": "next", built by @railcode/next. Proven on a real app, with gaps listed in the guide |
A container: a Dockerfile or docker-compose stack running a server in any language |
references/containers.md | Method and mappings built from the platform's documented behaviour; not yet backed by a recorded migration |