Add Discord bot (moderation, filters, scheduling, roles, invites, site integration)
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>
This commit is contained in:
55
server/src/utils/botInternalClient.js
Normal file
55
server/src/utils/botInternalClient.js
Normal file
@@ -0,0 +1,55 @@
|
||||
// Tiny fetch wrapper for calling the bot process's /internal/* API (shared
|
||||
// secret, same pattern as requireInternalKey on both sides). Used by the
|
||||
// Discord Bot admin controller to push config after a save and to poll live
|
||||
// status for the admin panel. Never throws — callers get { ok: false, error }
|
||||
// on any failure (bot unreachable, timeout, non-2xx) so an admin save/poll
|
||||
// never 500s just because the bot container is down or restarting.
|
||||
const log = require('./logger')('bot-internal-client')
|
||||
|
||||
const BASE_URL = process.env.BOT_INTERNAL_URL || 'http://localhost:4100'
|
||||
const KEY = process.env.BOT_INTERNAL_KEY || ''
|
||||
const TIMEOUT_MS = 4000
|
||||
|
||||
async function call(path, { method = 'GET', body } = {}) {
|
||||
const controller = new AbortController()
|
||||
const timeout = setTimeout(() => controller.abort(), TIMEOUT_MS)
|
||||
try {
|
||||
const res = await fetch(`${BASE_URL}${path}`, {
|
||||
method,
|
||||
headers: {
|
||||
'Content-Type': 'application/json',
|
||||
'X-Internal-Key': KEY,
|
||||
},
|
||||
body: body ? JSON.stringify(body) : undefined,
|
||||
signal: controller.signal,
|
||||
})
|
||||
if (!res.ok) {
|
||||
return { ok: false, error: `bot responded ${res.status}` }
|
||||
}
|
||||
return { ok: true, data: await res.json() }
|
||||
} catch (err) {
|
||||
log.warn('bot internal call failed', { path, message: err.message })
|
||||
return { ok: false, error: err.message }
|
||||
} finally {
|
||||
clearTimeout(timeout)
|
||||
}
|
||||
}
|
||||
|
||||
// Push a config change (start/stop the bot's Discord client).
|
||||
function pushConfig({ token, guildId, enabled }) {
|
||||
return call('/internal/config', { method: 'POST', body: { token, guildId, enabled } })
|
||||
}
|
||||
|
||||
// Live connection status, for the admin panel.
|
||||
function getStatus() {
|
||||
return call('/internal/status')
|
||||
}
|
||||
|
||||
// Site -> bot: a news post was published, post it to the configured #news
|
||||
// channel. Fire-and-forget from the caller's perspective — never throws, so
|
||||
// a bot outage never breaks publishing a post.
|
||||
function announce({ title, excerpt, url, imageUrl }) {
|
||||
return call('/internal/announce', { method: 'POST', body: { title, excerpt, url, imageUrl } })
|
||||
}
|
||||
|
||||
module.exports = { pushConfig, getStatus, announce }
|
||||
@@ -16,6 +16,13 @@ const pool = mariadb.createPool({
|
||||
insertIdAsNumber: true,
|
||||
bigIntAsNumber: true,
|
||||
decimalAsNumber: true,
|
||||
// The driver defaults to 'local' — silently serializing bound JS Date
|
||||
// params using the HOST MACHINE's local offset instead of the DB session's
|
||||
// timezone (discovered via the Discord bot's temp_roles.expires_at coming
|
||||
// back hours off in dev). 'auto' negotiates the actual session timezone so
|
||||
// Date round-trips correctly regardless of host TZ — affects any write of
|
||||
// a JS Date param, e.g. botConfig.model.js's last_connected_at.
|
||||
timezone: 'auto',
|
||||
})
|
||||
|
||||
/**
|
||||
|
||||
Reference in New Issue
Block a user