tiennm99 9e95db2851 refactor(modules): allow hyphens in module names
Relax module name regex to accept hyphens, preparing for hyphenated
loldle variants (loldle-emoji, loldle-quote, etc.) ported from upstream
JS sources. Storage prefix delimiter ':' remains rejected. Telegram
command names use separate stricter regex (commandNameRe) and are
unaffected.
2026-05-09 12:19:16 +07:00

miti99bot-go

Plug-n-play Telegram bot framework in Go, deployed on Google Cloud Run with Firestore + Gemini. Free-tier port of miti99bot.

Status

Early scaffolding. See plans/260508-2222-go-port-cloud-run/plan.md for the full roadmap.

Phase What Status
01 GCP setup, Cloud Run baseline pending
02 Repo bootstrap + webhook skeleton partial (local pieces done; Cloud Run deploy deferred to Phase 01)
03 Module framework + KVStore done
04+ Firestore, modules, cron, CI/CD, cutover pending

Layout

cmd/server/             entrypoint
internal/server/        HTTP routes (/, /webhook, /cron/{name})
internal/telegram/      Telegram webhook + bot wrapper
internal/modules/       Module framework, registry, dispatchers
internal/storage/       KVStore interface, in-memory impl, prefix wrapper

Run locally

TELEGRAM_BOT_TOKEN=\
TELEGRAM_WEBHOOK_SECRET=local \
PORT=8080 \
MODULES= \
go run ./cmd/server

End-to-end smoke test against a Telegram dev bot requires ngrok (local) or a Cloud Run deployment. The dev bot is created manually; token is injected via env vars only.

Test

go vet ./...
go test ./...

Build

docker build -t miti99bot-go .

The image is multi-stage (golang:1.23-alpinegcr.io/distroless/static:nonroot); resulting image is ~15 MiB.

License

Apache-2.0.

S
Description
Plug-n-play Telegram bot framework on Cloudflare Workers with grammY. Modules load via env var, three command visibility levels, KV storage behind a swappable interface.
Readme Apache-2.0 3.5 MiB
Languages
Go 98.1%
Makefile 1.5%
Shell 0.3%