Deploy Fizzy
Kanban tracking tool for issues and ideas by 37signals
Fizzy
Just deployed
/rails/storage
Deploy and Host Fizzy on Railway
Fizzy is a kanban tracking tool for tracking just about anything. Bugs, issues, ideas, small projects, it fits them all.
Fast, straightforward, and vibrant, it’s a blast of fresh air in a shockingly stale category.
About Hosting Fizzy
To deploy Fizzy, you must configure the following things via environment variables:
- SMTP: Fizzy currently uses magic links for logins, SMTP is needed to send these.
- VAPID: Fizzy uses the web push protocol for browser notifications. A link is included in the configuration stage to generate the public and private keys.
Additionally:
- It is recommended to enable teardown and setting draining to
30s. This ensures proper shutdown, and avoids the "crashed" state when redeploying.
Common Use Cases
- Lightweight, fast Kanban for teams to track bugs, ideas, and releases with public boards and Slack/webhook updates.
Dependencies for Fizzy Hosting
Deployment Dependencies
Why Deploy Fizzy on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Fizzy on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
SMTP_DOMAIN
Domain used in MAILER_FROM_ADDRESS
SMTP_ADDRESS
SMTP server host (for Resend; smtp.resend.com)
SMTP_PASSWORD
SMTP password (for Resend; set to API key)
SMTP_USERNAME
SMTP username (for Resend; resend)
VAPID_PUBLIC_KEY
Public key for browser push notifications (www.magicbell.com/web-push/vapid-keys)
VAPID_PRIVATE_KEY
Private key for browser push notifications
MAILER_FROM_ADDRESS
SMTP from address