Skip to content

feat: add Fizzy template blueprint #716

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adryserage wants to merge 7 commits into
base: canary
Choose a base branch
from
Open

feat: add Fizzy template blueprint #716

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f1cd2ae
feat: add Fizzy template blueprint
adryserage Feb 20, 2026
0033d8d
Update blueprints/fizzy/docker-compose.yml
adryserage Feb 20, 2026
1c96e4f
Update blueprints/fizzy/docker-compose.yml
adryserage Feb 20, 2026
838baca
Update blueprints/fizzy/template.toml
adryserage Feb 20, 2026
0f12c1f
Update meta.json
adryserage Feb 20, 2026
72aa05c
Update meta.json
adryserage Feb 20, 2026
d66c0e2
Update blueprints/fizzy/docker-compose.yml
adryserage Feb 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions blueprints/fizzy/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
version: "3.8"
services:
Comment thread
adryserage marked this conversation as resolved.
fizzy:
image: ghcr.io/basecamp/fizzy:1.0.0
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Docker image uses the :main tag which is a moving target similar to :latest. According to the project conventions, images should be pinned to specific versions to prevent templates from breaking when upstream images change unexpectedly. While :main is used in some other blueprints (e.g., aptabase, windmill), the recommended practice is to use a specific version tag or commit SHA. Consider pinning to a specific release version if available, or at minimum document that this template tracks the main branch and may experience breaking changes.

Copilot generated this review using guidance from repository custom instructions.
restart: unless-stopped

environment:
# Rails
RAILS_ENV: production
RAILS_LOG_TO_STDOUT: "1"

# Secrets
SECRET_KEY_BASE: ${SECRET_KEY_BASE:?set SECRET_KEY_BASE}
VAPID_PUBLIC_KEY: ${VAPID_PUBLIC_KEY:?set VAPID_PUBLIC_KEY}
VAPID_PRIVATE_KEY: ${VAPID_PRIVATE_KEY:?set VAPID_PRIVATE_KEY}

# Mail
MAILER_FROM_ADDRESS: ${MAILER_FROM_ADDRESS:?set MAILER_FROM_ADDRESS}
SMTP_ADDRESS: ${SMTP_ADDRESS:?set SMTP_ADDRESS}
SMTP_PORT: ${SMTP_PORT:-2525}
SMTP_USERNAME: ${SMTP_USERNAME:-}
SMTP_PASSWORD: ${SMTP_PASSWORD:-}

# Fizzy behavior
MULTI_TENANT: ${MULTI_TENANT:-false}
SOLID_QUEUE_IN_PUMA: ${SOLID_QUEUE_IN_PUMA:-true}

volumes:
# Contains SQLite DB + ActiveStorage
- fizzy_storage:/rails/storage

expose:
- "3000"

volumes:
fizzy_storage:
15 changes: 15 additions & 0 deletions blueprints/fizzy/fizzy.svg
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
33 changes: 33 additions & 0 deletions blueprints/fizzy/template.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
[variables]
main_domain = "${domain}"
secret_key_base = "${base64:64}"
vapid_public_key = "${base64:64}"
vapid_private_key = "${base64:64}"
mailer_from_address = "fizzy@${main_domain}"
smtp_address = "smtp.example.com"
smtp_port = "2525"
smtp_username = ""
smtp_password = ""
multi_tenant = "false"
solid_queue_in_puma = "true"

[config]
mounts = []

env = [
"SECRET_KEY_BASE=${secret_key_base}",
"VAPID_PUBLIC_KEY=${vapid_public_key}",
"VAPID_PRIVATE_KEY=${vapid_private_key}",
"MAILER_FROM_ADDRESS=${mailer_from_address}",
"SMTP_ADDRESS=${smtp_address}",
"SMTP_PORT=${smtp_port}",
"SMTP_USERNAME=${smtp_username}",
"SMTP_PASSWORD=${smtp_password}",
"MULTI_TENANT=${multi_tenant}",
"SOLID_QUEUE_IN_PUMA=${solid_queue_in_puma}",
]

[[config.domains]]
serviceName = "fizzy"
port = 3_000
host = "${main_domain}"
19 changes: 19 additions & 0 deletions meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2346,6 +2346,25 @@
"server"
]
},
{
"id": "fizzy",
"name": "Fizzy",
"version": "0.1.0",
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version field uses "main" which corresponds to the Docker image tag. According to project conventions, versions should be pinned to specific releases rather than tracking branch names like "main" to avoid unexpected breaking changes. While this matches the docker-compose.yml image tag, consider using a specific version number when Fizzy releases stable versions.

Copilot generated this review using guidance from repository custom instructions.
"description": "Fizzy is a Kanban-style tracker for issues and ideas from 37signals.",
"logo": "fizzy.svg",
"links": {
"github": "https://github.com/basecamp/fizzy",
"website": "https://fizzy.do/",
"docs": "https://github.com/basecamp/fizzy"
},
"tags": [
"kanban",
"project-management",
"issues",
"ideas",
"self-hosted"
]
},
{
"id": "flagsmith",
"name": "Flagsmith",
Expand Down
Loading