Clean resubmission of #581 (closed for inactivity). This PR only contains the Fizzy blueprint — no CI/workflow changes.
Docker Compose
\ghcr.io/basecamp/fizzy:main\
Expose port 3000 (no \ports:\ — uses Traefik)
SQLite volume for persistence
SMTP for emails, VAPID for push notifications
Greptile Summary
Adds Fizzy, a Kanban-style issue and idea tracker by 37signals (Basecamp), as a new template blueprint.
Key changes:
New blueprint with single-service Docker Compose setup using SQLite for persistence
Template configuration with SMTP for emails and VAPID keys for push notifications
Proper logo and metadata integration
Issues found:
Critical: Service name in docker-compose.yml is web but must be fizzy to match the blueprint folder name (per AGENTS.md line 46)
Required: Missing version: "3.8" declaration in docker-compose.yml (per AGENTS.md line 149)
Required: Service name in template.toml must also be updated to fizzy to match
Formatting: Extra indentation on opening brace in meta.json entry
These are straightforward fixes that maintain consistency with project conventions.
Confidence Score: 3/5
Safe to merge after fixing service naming convention violations
The template is well-structured and follows most conventions correctly, but has critical naming convention violations that will cause deployment issues. Service name must match blueprint folder name (fizzy not web) in both docker-compose.yml and template.toml, missing required version: "3.8" declaration, and minor formatting issue in meta.json. Once these syntax issues are resolved, the template will be production-ready.
blueprints/fizzy/docker-compose.yml and blueprints/fizzy/template.toml need service name corrections, meta.json needs indentation fix
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/716
**Author:** [@adryserage](https://github.com/adryserage)
**Created:** 2/20/2026
**Status:** ❌ Closed
**Base:** `canary` ← **Head:** `add/fizzy-template`
---
### 📝 Commits (7)
- [`f1cd2ae`](https://github.com/Dokploy/templates/commit/f1cd2ae78cb300114fabab19d7590b90f97799cb) feat: add Fizzy template blueprint
- [`0033d8d`](https://github.com/Dokploy/templates/commit/0033d8de86dd5ba4e46c0b5921340001c358cbc9) Update blueprints/fizzy/docker-compose.yml
- [`1c96e4f`](https://github.com/Dokploy/templates/commit/1c96e4f01f707f8fb8c723f0f850812034517926) Update blueprints/fizzy/docker-compose.yml
- [`838baca`](https://github.com/Dokploy/templates/commit/838baca3d940b1d6a6ba451d5c91bd70cff2f746) Update blueprints/fizzy/template.toml
- [`0f12c1f`](https://github.com/Dokploy/templates/commit/0f12c1f99c6197dca595520c46d479351f6b5f0b) Update meta.json
- [`72aa05c`](https://github.com/Dokploy/templates/commit/72aa05c46a6520ca8f17530b8b424d9c8702e7b9) Update meta.json
- [`d66c0e2`](https://github.com/Dokploy/templates/commit/d66c0e2e2dab928349e69b1107d02d054b75bffc) Update blueprints/fizzy/docker-compose.yml
### 📊 Changes
**4 files changed** (+103 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/fizzy/docker-compose.yml` (+36 -0)
➕ `blueprints/fizzy/fizzy.svg` (+15 -0)
➕ `blueprints/fizzy/template.toml` (+33 -0)
📝 `meta.json` (+19 -0)
</details>
### 📄 Description
## Summary
Adds [Fizzy](https://github.com/basecamp/fizzy), a Kanban-style issue and idea tracker by 37signals (Basecamp).
## Changes
- \lueprints/fizzy/docker-compose.yml\ — Single-service setup with SQLite storage
- \lueprints/fizzy/template.toml\ — SMTP, VAPID keys, Rails config
- \lueprints/fizzy/fizzy.svg\ — Logo
- \meta.json\ — Added Fizzy entry (alphabetical order)
## Context
Clean resubmission of #581 (closed for inactivity). This PR only contains the Fizzy blueprint — no CI/workflow changes.
## Docker Compose
- \ghcr.io/basecamp/fizzy:main\
- Expose port 3000 (no \ports:\ — uses Traefik)
- SQLite volume for persistence
- SMTP for emails, VAPID for push notifications
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
Adds Fizzy, a Kanban-style issue and idea tracker by 37signals (Basecamp), as a new template blueprint.
**Key changes:**
- New blueprint with single-service Docker Compose setup using SQLite for persistence
- Template configuration with SMTP for emails and VAPID keys for push notifications
- Proper logo and metadata integration
**Issues found:**
- **Critical**: Service name in `docker-compose.yml` is `web` but must be `fizzy` to match the blueprint folder name (per AGENTS.md line 46)
- **Required**: Missing `version: "3.8"` declaration in `docker-compose.yml` (per AGENTS.md line 149)
- **Required**: Service name in `template.toml` must also be updated to `fizzy` to match
- **Formatting**: Extra indentation on opening brace in `meta.json` entry
These are straightforward fixes that maintain consistency with project conventions.
<h3>Confidence Score: 3/5</h3>
- Safe to merge after fixing service naming convention violations
- The template is well-structured and follows most conventions correctly, but has critical naming convention violations that will cause deployment issues. Service name must match blueprint folder name (`fizzy` not `web`) in both `docker-compose.yml` and `template.toml`, missing required `version: "3.8"` declaration, and minor formatting issue in `meta.json`. Once these syntax issues are resolved, the template will be production-ready.
- `blueprints/fizzy/docker-compose.yml` and `blueprints/fizzy/template.toml` need service name corrections, `meta.json` needs indentation fix
<sub>Last reviewed commit: f1cd2ae</sub>
<!-- greptile_other_comments_section -->
**Context used:**
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/716
Author: @adryserage
Created: 2/20/2026
Status: ❌ Closed
Base:
canary← Head:add/fizzy-template📝 Commits (7)
f1cd2aefeat: add Fizzy template blueprint0033d8dUpdate blueprints/fizzy/docker-compose.yml1c96e4fUpdate blueprints/fizzy/docker-compose.yml838bacaUpdate blueprints/fizzy/template.toml0f12c1fUpdate meta.json72aa05cUpdate meta.jsond66c0e2Update blueprints/fizzy/docker-compose.yml📊 Changes
4 files changed (+103 additions, -0 deletions)
View changed files
➕
blueprints/fizzy/docker-compose.yml(+36 -0)➕
blueprints/fizzy/fizzy.svg(+15 -0)➕
blueprints/fizzy/template.toml(+33 -0)📝
meta.json(+19 -0)📄 Description
Summary
Adds Fizzy, a Kanban-style issue and idea tracker by 37signals (Basecamp).
Changes
Context
Clean resubmission of #581 (closed for inactivity). This PR only contains the Fizzy blueprint — no CI/workflow changes.
Docker Compose
Greptile Summary
Adds Fizzy, a Kanban-style issue and idea tracker by 37signals (Basecamp), as a new template blueprint.
Key changes:
Issues found:
docker-compose.ymliswebbut must befizzyto match the blueprint folder name (per AGENTS.md line 46)version: "3.8"declaration indocker-compose.yml(per AGENTS.md line 149)template.tomlmust also be updated tofizzyto matchmeta.jsonentryThese are straightforward fixes that maintain consistency with project conventions.
Confidence Score: 3/5
fizzynotweb) in bothdocker-compose.ymlandtemplate.toml, missing requiredversion: "3.8"declaration, and minor formatting issue inmeta.json. Once these syntax issues are resolved, the template will be production-ready.blueprints/fizzy/docker-compose.ymlandblueprints/fizzy/template.tomlneed service name corrections,meta.jsonneeds indentation fixLast reviewed commit:
f1cd2aeContext used:
dashboard- AGENTS.md (source)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.