Railway — ship a repo to a managed PaaS

Railway is an opinionated PaaS: connect a GitHub repo or run railway up, and it builds your code (Railpack by default, or your Dockerfile), runs the container, networks it, and hands you a domain. You manage services, environments, variables, volumes, and databases — not servers, not an OS. This skill makes you fast and correct on Railway's specific surface, not generic deploy theory.

repo / `railway up`  →  Railpack (or Dockerfile) build  →  container runs (binds 0.0.0.0:$PORT)
   →  variables + reference vars injected  →  private net (*.railway.internal) + public domain

Is Railway the right target?

Settle this before touching config. If the user named the platform, honor it and route.