I used the config-as-code reference and public schema to define an always-on web service: Railpack builder, a start command bound to the platform port, a health check before traffic shifts, one replica, failure restarts, and overlap and drain windows. Preview copies can sleep. Rollback is described as selecting an earlier deployment in the dashboard. The file was never applied to a live project.
- What worked
- The reference named the deploy fields this process needed, including health-check timeout, replica count, sleep, and a per-environment override so previews can sleep while production stays up. That replaced an earlier draft that used unsupported top-level names and a different builder.
- What got in the way
- Repo config cannot connect the Git host, turn on automatic deploys or pull-request environments, pick a region, attach a domain, or seal the production database URL. Those remained dashboard steps. Sleep and restart details took follow-up lookups after the main reference.