Claude
7a21cc636c
Standalone bot/ service (its own package.json/Dockerfile) managed entirely through a new admin-only Discord Bot panel — token stored encrypted in the DB and pushed to the bot process in-memory, never an env var. Built in phases, each independently verified against a live Discord guild: - Bot skeleton: gateway connection, internal shared-secret API, self-heals on its own restart by pulling config from the site - Moderation core: /ban /kick /mute /warn /warnings + mod-log channel - Word/invite/spam filtering with leetspeak-resistant normalization and a staff role/channel allowlist - Scheduled messages: recurring (cron) and one-off channel posts - Role assignment: button role menus, auto-role on join, temp roles, bulk role ops - Auto-rotating primary invite with an audit log - Site integration: news-publish -> Discord announce webhook, manual /announce, read-only /wiki search Also fixes a pre-existing bug in both DB pools (server + bot): the mariadb driver defaulted to timezone 'local', silently mis-serializing bound Date params by the host's local offset instead of the DB's UTC session. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
45 lines
2.1 KiB
Plaintext
45 lines
2.1 KiB
Plaintext
# ─── UOMysticmoon Discord bot — local dev environment ───
|
|
# Copy to bot/.env for running `npm run dev` outside Docker.
|
|
# (In Docker, the root .env / docker-compose provides these instead.)
|
|
#
|
|
# NOTE: there is no Discord bot token here on purpose. The token is entered
|
|
# in the admin panel (Discord Bot page), stored encrypted in the main site's
|
|
# DB, and pushed to this process in-memory over the internal API. It is
|
|
# never read from an env var and never written to this process's disk.
|
|
|
|
PORT=4100
|
|
|
|
# Logging — written to BOTH the console and a log file (default <bot>/logs/bot.log).
|
|
LOG_LEVEL=debug # console verbosity: error | warn | info | debug
|
|
FILE_LOG_LEVEL=debug # file verbosity
|
|
LOG_TO_FILE=true # set false for console-only
|
|
# LOG_DIR= # defaults to bot/logs
|
|
# LOG_FILE=bot.log
|
|
|
|
# Shared secret for the internal API between this bot and the main site
|
|
# (server/). MUST be byte-for-byte identical to BOT_INTERNAL_KEY in
|
|
# server/.env.example / the root .env.example — it is the only auth on both
|
|
# sides' /internal/* routes, so a mismatch silently breaks every server<->bot
|
|
# call with 401s. Generate one long random string and copy it to both places.
|
|
BOT_INTERNAL_KEY=dev-only-change-me-bot-key
|
|
|
|
# Where this bot calls back to the main site to fetch its config on boot
|
|
# (GET .../api/v1/internal/bot-config), so a restart self-reconnects without
|
|
# needing the admin panel to push config again.
|
|
SITE_INTERNAL_URL=http://localhost:3000/api/v1/internal/bot-config
|
|
|
|
# Read-only PUBLIC API base (Phase 7) — no shared secret, same data any
|
|
# visitor's browser can fetch. Used by /wiki (search) and /announce
|
|
# (re-post an existing news item).
|
|
SITE_PUBLIC_URL=http://localhost:3000/api/v1/public
|
|
|
|
# Database (Phase 2+) — same physical DB as the main site, but the bot only
|
|
# ever reads/writes its OWN tables (guild_config, mod_actions, warnings, and
|
|
# more in later phases). It never touches site tables (users, bot_config,
|
|
# etc.) directly. Point this at the same DB the server/ uses.
|
|
DB_HOST=127.0.0.1
|
|
DB_PORT=3306
|
|
DB_NAME=uomysticmoon
|
|
DB_USER=uomm
|
|
DB_PASSWORD=change-me-db-password
|