Files
DanConwayDev 28c881ba97 feat(deploy): add managed hosting templates
Agents need repeatable provider inputs instead of translating a generic container guide into mutable dashboard settings on every deployment.

Add Railway, Render, and Fly.io configurations that all build the canonical Dockerfile, mount /data, expose one HTTP service, allow bounded shutdown, and avoid overlapping writers. Pair them with provider-specific CLI and dashboard instructions, DNS verification, backup cautions, and one-instance constraints.

The templates assume each provider terminates TLS and preserves WebSocket upgrades. Render still requires a supported connected Git source for Blueprint automation, and provider credentials or account mutations are deliberately outside this commit.

Validated Railway and Render against their current published JSON schemas, parsed both TOML files and all YAML, checked Fly fields against its current official reference, verified local documentation links, and ran git diff --check. flyctl strict validation was not possible without a Fly access token.
2026-08-20 19:38:04 +00:00

13 lines
243 B
TOML

"$schema" = "https://railway.com/railway.schema.json"
[build]
builder = "DOCKERFILE"
dockerfilePath = "Dockerfile"
[deploy]
healthcheckPath = "/"
healthcheckTimeout = 300
restartPolicyType = "ALWAYS"
overlapSeconds = 0
drainingSeconds = 300