Setup Guide

Prerequisites

Go 1.25+
MongoDB Atlas cluster (managed, no local MongoDB service required)
Telegram bot token from BotFather

Development Docker Run

cp .env.example .env
# set TELEGRAM_BOT_TOKEN in .env
# set MONGODB_URI to your MongoDB Atlas connection string
# docker compose sets MONGODB_DATABASE=development for local development
docker compose -f compose.dev.yaml up --build

The Docker Compose service connects to MongoDB Atlas; there is no bundled local MongoDB. Ensure MONGODB_URI is set in .env.

Production Docker Run

Use this for production deployment:

cp .env.example .env
# set TELEGRAM_BOT_TOKEN in .env
# set MONGODB_URI to your MongoDB Atlas connection string
# MONGODB_DATABASE defaults to openai_status_bot (production)
docker compose up -d --build

Local Go Run

cp .env.example .env
# set TELEGRAM_BOT_TOKEN in .env
# set MONGODB_URI to your MongoDB Atlas connection string
# export TELEGRAM_BOT_TOKEN or source .env with your shell workflow
# MONGODB_DATABASE defaults to openai_status_bot
go run ./cmd/openai-status-bot

MongoDB Atlas connection is required; there is no local MongoDB fallback.

Verification

go test ./...
go build -o /tmp/openai-status-bot ./cmd/openai-status-bot

Then send /start to the Telegram bot and run /status. If the same token was previously used by a webhook deployment, startup clears that webhook before long polling begins.

Docker images include a health check against http://127.0.0.1:8080/healthz inside the container.

1.5 KiB Raw Permalink Blame History