Buzz Self Hosting

What it does

When your agent uses it

• Helping a user set up
• Operate a self-hosted Buzz relay through Docker Compose
• General Docker questions
• Non-Buzz Nostr deployments

Example prompts

• “/buzz-self-hosting”

Requirements

• Docker
• A credential in BUZZ_RELAY_PRIVATE_KEY
• A credential in BUZZ_GIT_HOOK_HMAC_SECRET

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1cd deploy/compose && cp .env.example .env, then edit .env
2. 2Set the URL block (BUZZ_DOMAIN, RELAY_URL, BUZZ_MEDIA_BASE_URL, BUZZ_MEDIA_SERVER_DOMAIN, BUZZ_CORS_ORIGINS) — all derive from one host…
3. 3./run.sh config (validates; catches leftover CHANGE_ME), then ./run.sh start. TLS on a public domain: BUZZ_COMPOSE_TLS=true ./run.sh start.
4. 4Liveness: curl -fsS http://127.0.0.1:3000/_liveness.
5. 5Register members: ./run.sh add-member for every human and every agent, with sleep 1 between adds (same-second roster events collide)…
6. 6Connect the desktop app with the exact RELAY_URL, create channels, add agents to channels, @mention.

What it can do on your machine

Read from SKILL.md and the folder at commit 3f2d570. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • docker
  • curl
  • openssl
  • bash

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use docker and curl, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • BUZZ_RELAY_PRIVATE_KEY
  • BUZZ_GIT_HOOK_HMAC_SECRET

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Buzz Self Hosting loads about 2.2k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 1,068 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~47

When it runs · the whole SKILL.md, loaded when a task matches

~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:24

  1. `cd deploy/compose && cp .env.example .env`, then edit `.env`:

• NoteMentions a .env fileSKILL.md:27

  entity. Set once, never rotate; back up `.env` itself.

• NoteMentions a .env fileSKILL.md:55

  docker compose --env-file .env -f compose.yml logs relay --since 10m | grep '"Event ingested via pipeline"'

• NoteMentions a .env fileSKILL.md:80

  - `$EDITOR .env` is a Unix-ism; PowerShell users should `notepad .env`.

• NoteMentions a .env fileSKILL.md:81

  - A file named `.env` looks nameless in Explorer unless "File name extensions" is on.

• NoteMentions a .env fileSKILL.md:86

  → MinIO console `:9001` (S3 creds from `.env`), Adminer `:8082` (server `postgres`, user `buzz`), Prometheus `:9090`. H

• NoteMentions a .env fileSKILL.md:87

  ata is local: `docker compose --env-file .env -f compose.yml exec -T postgres psql -U buzz -d buzz -c "SELECT kind, left

• NoteMentions a .env fileSKILL.md:95

  copy .env <backup-dir>\env-backup.txt

• NoteMentions a .env fileSKILL.md:96

  docker compose --env-file .env -f compose.yml exec -T postgres pg_dump -U buzz buzz > <backup-dir>\buzz-db.sql

• NoteMentions a .env fileSKILL.md:101

  `.env` is part of the backup — restoring data volumes without its keys restores nothing.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tonbistudio/buzz-skills at commit 3f2d570, republished under its MIT licence (© tonbistudio). 1,068 words, ~2,247 tokens.

name

buzz-self-hosting

description

Use when helping a user set up, debug, or operate a self-hosted Buzz relay through Docker Compose. Do not use for general Docker questions or non-Buzz Nostr deployments.

version

1.0.0

curl -s -o /dev/null -w "%{http_code}\n" -H "Connection: Upgrade" -H "Upgrade: websocket" \
  -H "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==" -H "Sec-WebSocket-Version: 13" http://<host>:3000/

docker compose --env-file .env -f compose.yml logs relay --since 10m | grep '"Event ingested via pipeline"'

copy .env <backup-dir>\env-backup.txt
docker compose --env-file .env -f compose.yml exec -T postgres pg_dump -U buzz buzz > <backup-dir>\buzz-db.sql
docker run --rm -v buzz-prod_buzz-minio-data:/data -v <backup-dir>:/backup alpine tar czf /backup/minio-data.tar.gz -C /data .
docker run --rm -v buzz-prod_buzz-git-data:/data -v <backup-dir>:/backup alpine tar czf /backup/git-data.tar.gz -C /data .

© tonbistudio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in buzz-self-hosting of tonbistudio/buzz-skills.

• SKILL.md
• evals/evals.json

Open the folder on GitHubat commit 3f2d570