Railway

Promptfree, for everyone, and the only version there is

Open the prompt in Claude CodeOpen the prompt in CodexOpen the prompt in Cursor

Copy

Set me up so a new service and its database are one command on my own server.

STACK
- Docker Compose as the unit of a project, one directory per environment
- Caddy in front with automatic TLS, Postgres and Redis as containers
- A deploy script over SSH that pulls, builds and rolls

PROJECT LAYOUT
- environments/{production,staging}/compose.yml plus an env file that is never committed
- A template command that scaffolds a new service with health check, limits and logging already set

NETWORKING
- Services reachable by name on an internal network; only Caddy is published
- Postgres and Redis never exposed to the host's public interface

DEPLOY
- Build, start the new container, wait for its health check, then swap the Caddy upstream and stop the old one
- Keep the previous image tagged so a rollback is one command

DATA
- Named volumes for Postgres and Redis, backed up nightly with pg_dump plus a volume snapshot to S3-compatible storage
- Restore script included, and a note that it has to be tested

ENVIRONMENTS
- Staging is the same compose file with a different env file and its own database
- Never share a database between environments; the README should say why

COST
- Record CPU and memory per service weekly, so the machine can be sized honestly

Include a README with the scaffold command, the rollback command and the backup schedule.