Portainer Templates logo

Portainer Templates

Fizzy Fizzy

Stack

Productivity Pm

Fizzy - 37signals' free, open-source kanban: fast, focused boards for bugs, issues, ideas, and small projects.

Image details

Architecture: amd64, arm64
Image size: 209 MB
User: basecamp

Source details

Repo: basecamp/fizzy
Stars: 8k
Forks: 1k
Language: Ruby
Latest: fizzy@477c943 · 1 day ago
Updated: 1 day ago
Website: fizzy.do/

Configuration

Type
Compose
Platform
linux
Image
ghcr.io/basecamp/fizzy:sha-62d3cad
Ports
5000:5000
Volumes
/rails/storage : storage
Env vars
HTTP_PORT=5000DISABLE_SSL=trueSECRET_KEY_BASE=${SECRET_KEY_BASE}BASE_URL=${BASE_URL:-http://localhost:5000}MAILER_FROM_ADDRESS=${MAILER_FROM_ADDRESS:-}SMTP_ADDRESS=${SMTP_ADDRESS:-}SMTP_PORT=${SMTP_PORT:-587}SMTP_USERNAME=${SMTP_USERNAME:-}SMTP_PASSWORD=${SMTP_PASSWORD:-}VAPID_PUBLIC_KEY=${VAPID_PUBLIC_KEY:-}VAPID_PRIVATE_KEY=${VAPID_PRIVATE_KEY:-}
Restart
unless-stopped
Source
Repo

Template by deployable-sh·Source

Report issue

Standalone Install

Select an install method, to see config/commands for deploying Fizzy

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Fizzy, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

name: fizzy

services:
  fizzy:
    image: ghcr.io/basecamp/fizzy:sha-62d3cad
    restart: unless-stopped
    environment:
      HTTP_PORT: "5000"
      DISABLE_SSL: "true"
      SECRET_KEY_BASE: ${SECRET_KEY_BASE}
      BASE_URL: ${BASE_URL:-http://localhost:5000}
      MAILER_FROM_ADDRESS: ${MAILER_FROM_ADDRESS:-}
      SMTP_ADDRESS: ${SMTP_ADDRESS:-}
      SMTP_PORT: ${SMTP_PORT:-587}
      SMTP_USERNAME: ${SMTP_USERNAME:-}
      SMTP_PASSWORD: ${SMTP_PASSWORD:-}
      VAPID_PUBLIC_KEY: ${VAPID_PUBLIC_KEY:-}
      VAPID_PRIVATE_KEY: ${VAPID_PRIVATE_KEY:-}
    ports:
      - "5000:5000"
    volumes:
      - storage:/rails/storage

volumes:
  storage:

Or deploy it directly from the source:

git clone https://github.com/deployable-sh/stacks
cd stacks
docker compose -f fizzy/compose.yaml up -d

More install options in our documentation, or see basecamp/fizzy for app-specific guidance.

Fizzy

This is the source code of Fizzy, the Kanban tracking tool for issues and ideas by 37signals.

Running your own Fizzy instance

The easiest way to self-host Fizzy is with ONCE. It will guide you through the initial setup, and keep your instance up to date automatically. It has everything you need for a fully-functional, single-machine deployment.
To get started, run this on the machine where you want to install Fizzy:
curl https://get.once.com/fizzy | sh

Deploying with Docker

If you'd rather run our pre-built Docker image yourself, you can find the details in our Docker deployment guide.

Deploying with Kamal

If you want more flexibility to customize your Fizzy installation by changing its code, and deploy those changes to your server, then we recommend you deploy Fizzy with Kamal. You can find a complete walkthrough of doing that in our Kamal deployment guide.

Development

You are welcome -- and encouraged -- to modify Fizzy to your liking. Please see our Development guide for how to get Fizzy set up for local development.

Contributing

We welcome contributions! Please read our style guide before submitting code.

License

Fizzy is released under the O'Saasy License.

Serve Fizzy on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying fizzy.example.com to http://fizzy:5000

Add this to your Caddyfile

fizzy.example.com {
	reverse_proxy http://fizzy:5000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5000 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5000
  • Stop the other service, or pick a different host port. In 5000:5000 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, fizzy can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5000

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/basecamp/fizzy:sha-62d3cad

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Fizzy is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Fizzy needs bundled into one download. This template pulls ghcr.io/basecamp/fizzy:sha-62d3cad, which Docker fetches once (about 209 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Fizzy's comes from the GitHub Container Registry, published by basecamp.

Version tags

The bit after the colon in the image name is the version tag. This one pins sha-62d3cad, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 5000:5000 means it's reachable on port 5000 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5000:5000

Volumes

A volume is where Fizzy keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /rails/storage kept in the storage volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Fizzy takes 11 of them, all with defaults you can leave alone or tweak:

  • HTTP_PORT, defaults to 5000
  • DISABLE_SSL, defaults to true
  • SECRET_KEY_BASE, pulled from your own environment. Rails secret - a long random string.
  • BASE_URL, defaults to http://localhost:5000. The app's public URL (https domain on Miget).
  • MAILER_FROM_ADDRESS, pulled from your own environment. Optional: email for invites and notifications.
  • SMTP_ADDRESS, pulled from your own environment
  • SMTP_PORT, defaults to 587
  • SMTP_USERNAME, pulled from your own environment
  • SMTP_PASSWORD, pulled from your own environment
  • VAPID_PUBLIC_KEY, pulled from your own environment. Optional: Web Push (browser notifications).
  • VAPID_PRIVATE_KEY, pulled from your own environment

Restart policy

The restart policy here is unless-stopped, so Docker restarts Fizzy after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Fizzy sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container fizzy. That's what you'll spot in the containers list and use in commands like docker logs fizzy.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Fizzy up. Add the template list to Portainer once, then deploying Fizzy is a click rather than a wall of config.