[PR #1030] feat: add Bonfire template #16338

New Issue

GiteaMirror · 2026-07-14T23:19:42-05:00

GiteaMirror commented

2026-07-14 23:19:42 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/1030
Author: @Siumauricio
Created: 7/14/2026
Status: 🔄 Open

Base: canary ← Head: feat/bonfire

📝 Commits (1)

7d252ea feat: add bonfire template

📊 Changes

4 files changed (+157 additions, -0 deletions)

View changed files

➕ blueprints/bonfire/bonfire.svg (+1 -0)
➕ blueprints/bonfire/docker-compose.yml (+84 -0)
➕ blueprints/bonfire/meta.json (+17 -0)
➕ blueprints/bonfire/template.toml (+55 -0)

📄 Description

Closes #125

Adds a blueprint for Bonfire (social flavour), the federated social networking toolkit.

Why now

Bonfire spent years in beta, but it has been out of beta for a while: 1.0 shipped in 2025 and upstream now cuts regular stable releases (1.0.1 through 1.0.5, the latter released 2026-06-30) with maintained Docker images (bonfirenetworks/bonfire:<version>-social-amd64).

Stack

Service	Image	Notes
`bonfire`	`bonfirenetworks/bonfire:1.0.5-social-amd64`	official release image, migrations run automatically on startup
`db`	`postgis/postgis:17-3.5-alpine`	upstream's default database image (PostGIS extension is required)
`search`	`getmeili/meilisearch:v1.11`	the Meilisearch version pinned by upstream's `docker-compose.release.yml`

Mirrors upstream's reference deployments (docker-compose.release.yml + the coop-cloud recipe): named volumes for uploads/db/search data, healthchecks on bonfire and db, all secrets generated by template variables.

Notes

DB_MIGRATE_INDEXES_CONCURRENTLY=false is set explicitly: without it the initial migrations try CREATE INDEX CONCURRENTLY inside a transaction and fail (upstream sets the same default in config/templates/public.env and in the coop-cloud recipe).
PUBLIC_PORT defaults to 80 so links work on a plain-HTTP domain out of the box; the template documents switching it to 443 once HTTPS is enabled (required for federation).
The first account to sign up becomes the instance admin and does not need email confirmation, so the template works without a mail backend. Further signups are invite-only by default (admin can create invites or open signups in the instance settings); SMTP/API mail backends are documented as commented env vars.

Tested

Deployed on a Dokploy instance from this exact blueprint:

deploy reaches done, all 3 containers healthy
GET / → 200 "Explore local activities · Bonfire social"
GET /signup → 200 signup form (after initial migrations complete)
GET /.well-known/nodeinfo → federation endpoints respond

🤖 Generated with Claude Code

_{🔄 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/1030 **Author:** [@Siumauricio](https://github.com/Siumauricio) **Created:** 7/14/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `feat/bonfire` --- ### 📝 Commits (1) - [`7d252ea`](https://github.com/Dokploy/templates/commit/7d252ead5cc99489c82654483c79a20d440ebcca) feat: add bonfire template ### 📊 Changes **4 files changed** (+157 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/bonfire/bonfire.svg` (+1 -0) ➕ `blueprints/bonfire/docker-compose.yml` (+84 -0) ➕ `blueprints/bonfire/meta.json` (+17 -0) ➕ `blueprints/bonfire/template.toml` (+55 -0) </details> ### 📄 Description Closes #125 Adds a blueprint for [Bonfire](https://bonfirenetworks.org) (social flavour), the federated social networking toolkit. ## Why now Bonfire spent years in beta, but it has been out of beta for a while: 1.0 shipped in 2025 and upstream now cuts regular stable releases (`1.0.1` through `1.0.5`, the latter released 2026-06-30) with maintained Docker images (`bonfirenetworks/bonfire:<version>-social-amd64`). ## Stack | Service | Image | Notes | | --- | --- | --- | | `bonfire` | `bonfirenetworks/bonfire:1.0.5-social-amd64` | official release image, migrations run automatically on startup | | `db` | `postgis/postgis:17-3.5-alpine` | upstream's default database image (PostGIS extension is required) | | `search` | `getmeili/meilisearch:v1.11` | the Meilisearch version pinned by upstream's `docker-compose.release.yml` | Mirrors upstream's reference deployments (`docker-compose.release.yml` + the coop-cloud recipe): named volumes for uploads/db/search data, healthchecks on `bonfire` and `db`, all secrets generated by template variables. ## Notes - `DB_MIGRATE_INDEXES_CONCURRENTLY=false` is set explicitly: without it the initial migrations try `CREATE INDEX CONCURRENTLY` inside a transaction and fail (upstream sets the same default in `config/templates/public.env` and in the coop-cloud recipe). - `PUBLIC_PORT` defaults to `80` so links work on a plain-HTTP domain out of the box; the template documents switching it to `443` once HTTPS is enabled (required for federation). - The first account to sign up becomes the instance admin and does not need email confirmation, so the template works without a mail backend. Further signups are invite-only by default (admin can create invites or open signups in the instance settings); SMTP/API mail backends are documented as commented env vars. ## Tested Deployed on a Dokploy instance from this exact blueprint: - deploy reaches `done`, all 3 containers healthy - `GET /` → 200 "Explore local activities · Bonfire social" - `GET /signup` → 200 signup form (after initial migrations complete) - `GET /.well-known/nodeinfo` → federation endpoints respond 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-14 23:19:42 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#16338