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>
18 lines
602 B
JavaScript
18 lines
602 B
JavaScript
const db = require('../db')
|
|
|
|
async function add({ guildId, channelId, messageId, mapping, createdBy }) {
|
|
await db.query(
|
|
`INSERT INTO role_menus (guild_id, channel_id, message_id, mapping, created_by)
|
|
VALUES (?, ?, ?, ?, ?)`,
|
|
[guildId, channelId, messageId, JSON.stringify(mapping), createdBy || null],
|
|
)
|
|
}
|
|
|
|
async function getByMessageId(messageId) {
|
|
const rows = await db.query('SELECT * FROM role_menus WHERE message_id = ? LIMIT 1', [messageId])
|
|
if (!rows[0]) return null
|
|
return { ...rows[0], mapping: JSON.parse(rows[0].mapping) }
|
|
}
|
|
|
|
module.exports = { add, getByMessageId }
|