Deploy and Host Pulse Baseline on Railway

Pulse Baseline provisions the stable Railway control plane used by pulse-railway init before Pulse app deployments are rolled out.

About Hosting Pulse Baseline

This template creates three baseline services:

• pulse-router routes HTTP and WebSocket traffic to the active Pulse deployment.
• pulse-redis stores active deployment state, drain state, and shared Railway session data.
• pulse-janitor removes drained deployment services after connected clients reload.

The template is intentionally small. pulse-railway init deploys it first, then writes the runtime variables, domains, health checks, cron settings, and image pins needed by the installed plugin version.

Why Deploy Pulse Baseline on Railway?

Railway gives Pulse a simple place to run a persistent router, shared Redis, and cleanup job next to each app deployment. That keeps the app deploy flow focused on creating new backend services while the baseline handles traffic affinity, WebSocket routing, and old deployment cleanup.

Common Use Cases

• Bootstrap the baseline stack for pulse-railway deployments.
• Inspect the control-plane services used by the Pulse Railway plugin.
• Test router, Redis, and janitor behavior independently from an app rollout.

Dependencies for Pulse Baseline

Use pulse-railway init for normal setup. Manual deployment is mainly useful for template inspection or debugging.

Deployment Dependencies

• ghcr.io/erwinkn/pulse-railway-router
• ghcr.io/erwinkn/pulse-railway-janitor
• Redis 8 with a Railway volume
• A Pulse app deployed later with pulse-railway deploy