2058713e03
- Added a `warningNumber` field to the `Warning` model for sequential identification of warnings. - Updated the `createWarning` function to handle the new `warningNumber` logic and notify users via DM upon receiving a warning. - Refactored moderation commands to utilize the new warning system, including changes to the warning creation and removal processes. - Enhanced the WebUI to display warning numbers in the warnings table and updated localization for related messages. - Documented changes in phase tracking to reflect the new warning system features.
Nexumi
Nexumi is a public Discord bot with dashboard architecture, built as a TypeScript monorepo.
Phase 1 scope
- Monorepo foundation with
apps/botandpackages/shared - PostgreSQL + Redis compose stack
- Prisma core schema (
Guild,GuildSettings,User,Case) plus moderation tables (Warning,ModNote) - Command and module framework for slash command routing
- Permission layer and i18n starter (
de+en) - BullMQ integration for persistent moderation jobs (temp-ban expiration)
- Complete moderation reference command set for Phase 1
Quickstart
- Copy
.env.exampleto.envand fill required values. - Install dependencies:
pnpm install
- Generate Prisma client:
pnpm prisma:generate
- Apply database migrations:
pnpm prisma:migrate
- Start stack:
docker compose up -d
- Start bot locally:
pnpm --filter @nexumi/bot dev
Verification commands
pnpm typecheckpnpm lintpnpm test
Database
See docs/DATABASE.md for migrations, backup and restore runbooks.
Backup and restore note
Phase 1 includes the BullMQ foundation for scheduled jobs. Database backup rotation is configured via BACKUP_RETENTION_DAYS and the backups volume is already reserved in compose.
Restore flow (manual, PostgreSQL container):
- Stop bot/web services.
- Copy dump into postgres container.
- Run
psqlrestore againstnexumidatabase:docker compose exec -T postgres psql -U nexumi -d nexumi < /path/to/backup.sql
- Start services again.