Setting Up the Bunker Bot

You'll end up with five things. Every one of them should be owned by the club, not by you.

To copy IDs out of Discord you need Developer Mode on: User Settings → Advanced → Developer Mode. Keep a scratch note open — you'll collect about twenty values.

1. Create the integration. notion.so/my-integrations → New integration → name it Bunker Bot → the club workspace → Internal. Under Capabilities tick Read, Update and Insert content. Save and copy the Internal Integration Secret — it starts ntn_. That's NOTION_TOKEN.
2. Connect the databases. Open the Club Operations page → ••• → Connections → Bunker Bot. That grants every database under it at once. Then check each of the eleven below individually — a database created after the page was connected is not connected automatically.
3. Collect the data source IDs. They're fixed for this workspace and already filled in below; if you ever rebuild a database, its ID changes and the matching variable has to follow.

The first three are required; the Worker refuses to start without them. The rest each switch on one feature and the bot says what's missing if you use a command that needs one.

1. Create the application. discord.com/developers/applications → New Application → Bunker Bot.
2. Move it to a Team, now. Settings → Team → create or pick one → transfer. An app owned by a person's account dies with that account.
3. Copy two values from General Information: Application ID → DISCORD_APP_ID, Public Key → DISCORD_PUBLIC_KEY.
4. Bot → Reset Token → copy it (shown once) → DISCORD_BOT_TOKEN. Turn Public Bot off.
5. Invite it. OAuth2 → URL Generator → scopes bot and applications.commands → permissions Send Messages, Embed Links, Manage Events → open the URL → pick the server.
6. Collect three IDs from the server: right-click the server → Copy Server ID → DISCORD_GUILD_ID. Server Settings → Roles → E-Board → Copy Role ID → EBOARD_ROLE_ID. You'll collect channel IDs in a later step.

Leave the developer tab open. You come back for the endpoint URL after the Worker exists.

1. Create it. dash.cloudflare.com on the club Gmail → Workers & Pages → Create → Hello World → name it bunker-bot → Deploy. Note its URL: https://bunker-bot.<something>.workers.dev. That's PUBLIC_BASE, with no trailing slash.
2. Paste the code. Edit code → select all → paste the whole of worker.js → Deploy.
3. Bind the storage. Settings → Bindings → Add:

   Binding name	Type	Create it as
   CACHE	KV namespace	bunker-cache
   IMG	R2 bucket	bunker-images
   AUDIO	R2 bucket	bunker-audio

   The names on the left must match exactly — the code looks for env.CACHE. Photos, recordings, transcripts and the label queue all live in these; nothing else is stored anywhere.
4. Variables and secrets. Settings → Variables and Secrets. Use Secret for anything marked 🔒.

   Name		Value
   DISCORD_APP_ID		from Discord
   DISCORD_PUBLIC_KEY		from Discord
   DISCORD_BOT_TOKEN	🔒	from Discord
   DISCORD_GUILD_ID		the server
   EBOARD_ROLE_ID		the E-Board role
   NOTION_TOKEN	🔒	ntn_…
   REGISTER_SECRET	🔒	make one up — 20 random characters
   PRINT_SECRET	🔒	a different random string; it goes on the Pi
   PUBLIC_BASE		the Worker's own URL, no trailing slash
   TZ_OFFSET		-4
   INVENTORY_DS … FEEDBACK_DS		the eleven IDs above

5. The cron. Settings → Triggers → Cron Triggers → Add → */10 * * * *. Every scheduled job hangs off this one trigger.
6. Deploy again. Variables and bindings do not take effect until you do. This is the single most common way to lose twenty minutes.
7. Smoke test. Open PUBLIC_BASE/health. missing should be empty and items should be the size of the inventory. If Notion is failing, fix it here before touching Discord.

1. Point Discord at the Worker. Developer portal → General Information → Interactions Endpoint URL = PUBLIC_BASE/ with the trailing slash → Save. Discord sends a signed ping and a deliberately bad one; if it saves, signature verification works. If it refuses, DISCORD_PUBLIC_KEY is wrong or the Worker isn't deployed.
2. Register the commands. Open PUBLIC_BASE/register?secret=<REGISTER_SECRET>. Expect status: 200. Commands appear in the server instantly. Re-run this every time a command or one of its options changes.
3. Try it. /help in any channel. Then /find something.

Two free API keys, both on the club Gmail. Without them everything works except /notes.

You don't need to pick a Gemini model. The Worker queries the live model list, picks the best flash-class one, and remembers it — and if that model is ever retired it rediscovers by itself. GEMINI_TEXT_MODEL exists if you ever want to pin one.

Six channels, all optional, each one a variable. Make the private ones private and add the bot to them — a bot that isn't in a channel posts nothing and says nothing about it.

Right-click a channel → Copy Channel ID. Add the variables, deploy, and post the permanent check-in button once with /checkin-button, then pin it.

A Raspberry Pi in the bunker polls the Worker for labels and prints them. It needs only outbound Wi-Fi — no port forwarding, no domain, no tunnel.

1. Raspberry Pi OS on the Pi 3, on the bunker Wi-Fi, SSH on.
2. Copy the bunker-labels folder over and run bash install.sh. It installs the dependencies, renders a preview label, and installs the service.
3. Edit config.toml. [worker] base is PUBLIC_BASE; secret is PRINT_SECRET. Leave the backend on dryrun for now.
4. sudo systemctl start labeld, then in Discord /label item:BURC-0001. The Pi's log (journalctl -u labeld -f) should show the job and write a PNG to out/. /health now shows printer_last_seen.
5. Pick a printer. The README in the folder walks through it — the Epson over Ethernet (a ten-minute test says whether it needs a driver or not), a Brother QL over USB, or anything CUPS can see. Set the backend, restart the service, print one, stick it on something.

Hosted on the same Cloudflare account, free, with no domain needed.

1. Cloudflare dashboard → Workers & Pages → Create → Pages → Upload assets.
2. Name it bunker-docs. Drag the docs folder in. Deploy.
3. It's live at https://bunker-docs.pages.dev. Pin that in #general.

To update, upload the folder again — same project, new deployment, same URL. If the club ever gets access to its domain, Pages → Custom domains adds it in two clicks; nothing else changes.

1. Check the file as a module first: cp worker.js /tmp/x.mjs && node --check /tmp/x.mjs. Plain node --check worker.js parses it as CommonJS and misses module-only syntax errors.
2. Edit code → select all → paste → Deploy.
3. New variable or binding? Deploy again.
4. New command or option? /register?secret=….
5. New Notion database? Connect it to the integration.
6. Open /health and read it.
7. Twice a year: TZ_OFFSET is -4 from March and -5 from November. Nobody else will remember.