496a8239a5
- Changed NODE_ENV from development to production in .env.example for production readiness. - Updated WEBUI_URL to point to the new public URL behind Traefik. - Added internal and external networks in docker-compose.yml for improved service isolation and routing. - Removed direct port exposure for the WebUI, ensuring it is only accessible through Traefik. - Refactored landing and login pages in the WebUI to streamline navigation and error handling, redirecting users appropriately based on session status.
Nexumi
Nexumi is a self-hosted 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.