---
title: "Deploy Fizzy + MySQL"
description: "Kanban as it should be. Not as it has been."
category: "Other"
url: https://railway.com/deploy/fizzy-with-mysql
---

# Deploy Fizzy + MySQL

Kanban as it should be. Not as it has been.

**[Deploy Fizzy + MySQL on Railway](https://railway.com/template/fizzy-with-mysql)**

- **Creator:** Techulus
- **Category:** Other
- **Total deploys:** 3

## Template content

### fizzy https://www.fizzy.do/assets/images/logo.png

- **Source:** basecamp/fizzy
- **Public domain:** Yes

### MySQL https://devicons.railway.app/i/mysql.svg

- **Image:** mysql:9.4
- **Start command:** `docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --innodb-buffer-pool-size=1G`

## Buckets

- **active-storage**

## Documentation

# Deploy and Host Fizzy on Railway

The Kanban tracking tool for issues and ideas by 37signals.

## About Hosting Fizzy

Fizzy is a self-hosted Rails application that uses SQLite for data storage and Solid Queue for background job processing. Deploying on Railway requires
  configuring persistent storage for SQLite databases, setting up SMTP for passwordless authentication via magic links, and configuring environment variables
  for security. The application runs in a container with background job processing handled by Solid Queue inside the Puma web server. Once configured,
  Fizzy provides a collaborative kanban board system for teams to track cards, manage workflow columns, and organize work with automatic card postponement
  based on inactivity.

## Common Use Cases

  - Small to medium-sized teams needing a lightweight, self-hosted project management tool without database server overhead
  - Organizations requiring passwordless authentication and email-based access control for secure team collaboration
  - Development teams tracking bugs, features, and ideas across multiple boards with customizable workflow stages
  - Remote teams needing real-time collaboration features like comments, mentions, assignments, and activity timelines

## Dependencies for Fizzy

  - Railway Volume: Persistent storage mounted at `/rails/storage` for SQLite databases and file uploads
  - SMTP Service: Email provider (Mailgun, SendGrid, Amazon SES, etc.) for sending magic link authentication emails
  - Environment Variables: SECRET_KEY_BASE (128-char hex), SMTP credentials, APP_HOST, and configuration flags

### Deployment Dependencies

  - https://docs.railway.app/develop/cli (optional, for local deployment management)
  - https://guides.rubyonrails.org/security.html#custom-credentials (for understanding SECRET_KEY_BASE)
  - https://github.com/basecamp/solid_queue (background job system)

## 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.

## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/fizzy-with-mysql