Deploy and Host Launch Board

Launch Board is a polished Python + HTMX full-stack starter powered by Chirp. It is useful immediately and small enough to understand in a few minutes.

About Hosting

Railway builds the locked Python 3.14 application with Railpack, starts it with the explicit python app.py command, and verifies readiness at /ready. The template creates one public service, resolves the production environment, and generates a unique 64-character application secret. You enter no configuration.

The checklist is intentionally stored in a signed per-browser session cookie. It demonstrates the complete interaction architecture without claiming shared or durable persistence; the source keeps a clear seam for replacing that state with PostgreSQL later.

Why Deploy Launch Board on Railway

One Railway service and zero required configuration.
Full-page HTML plus HTMX fragments from the same named-block template.
Validated normal forms, out-of-band progress updates, and SSE live status.
Generated production secret, readiness checks, locked dependencies, and a cost-bounded single worker.
No JavaScript build pipeline, database, Redis, login, or external provider.

Common Use Cases

Learn server-rendered Python and HTMX through a complete working application.
Start an internal checklist, launch tracker, or lightweight workflow tool.
Evaluate Chirp's typed Page, Fragment, OOB, MutationResult, and EventStream architecture without assembling a frontend toolchain.
Replace the session repository with PostgreSQL as shared persistence becomes necessary.

Dependencies for Launch Board Hosting

The repository locks Chirp 0.10.0 and its Python dependencies with uv.lock. Railway supplies the port and production environment; the template generates the only application secret.

Deployment Dependencies

Python 3.14 via the committed .python-version.
Railpack and uv for reproducible installation.
One public Railway application service.
No database, volume, worker service, Redis, or third-party account.

Try and Customize

Start in templates/index.html to change the interface, styles.css to change the visual system, and app.py to add routes or replace the state repository. Production and local development use the same explicit python app.py entry point.