Discobot — Discord bot platform

1. 1

   Sign-in

   The user signs in with Discord, then authorises the bot on a server; their plan quota is checked before authorisation and on return.

2. 2

   Configuration

   They enable a plugin in the dashboard and set its options, validated against the plugin’s schema.

3. 3

   Event

   A Discord event — a member joining, a reaction, a command — reaches the bot worker.

4. 4

   Decision

   The bot calls the Laravel API with its token; the relevant PHP plugin returns the list of actions to perform.

5. 5

   Execution

   The executor carries out the actions with discord.js: send a message, add a role, open a ticket channel…

6. 6

   Feedback

   Each action’s result goes back to Laravel, which logs it and streams it live to the dashboard.

The main entities, their key fields and their relations.

Languages

PHP 8.3, JavaScript (ES modules)

Framework

Laravel 12

Front end

Livewire 3, Alpine 3, Tailwind 4, Vite 7

Bot

Node.js, discord.js 14, Express 5, node-cron; the bot runs in a worker thread

Database

MariaDB 11 in development, MySQL 8 in CI

Queues and cache

Laravel default and discord queues, Redis 7

Real time

Laravel Reverb, six broadcast events

Search

Laravel Scout and Meilisearch over the action log

Authentication

Discord OAuth2 through Socialite, Sanctum

Payments

Stripe Checkout subscriptions, verified webhook, grace period

Hosting

Multi-stage Docker, Docker Compose (app, queue, scheduler, Reverb, bot), image published to GHCR for amd64 and arm64

CI/CD

3 GitHub Actions workflows on a self-hosted runner: PHPUnit, Pest, Node tests, Pint, Composer and npm audits

Tests

PHPUnit 11 and Pest 3 (about 800 tests), Playwright (15 tests), node --test (15 tests)

Quality

Pint, Scribe API docs, Codecov coverage

Observability

Sentry, PostHog, in-house observability package, Pail

Security

Shared Bearer token between Laravel and the bot, compared in constant time on both sides; rate limiting; Ed25519 signature of Discord interactions verified

• Welcome and goodbye

  Custom messages when members join and leave.

• Reaction roles

  A role granted or removed depending on the reaction.

• Tickets

  Categories, claiming and transcripts.

• Invite tracking

  Who invited whom, suspicious invites flagged, top 10.

• Announcements

  Written in a Discord modal.

• Channel cleaner

  Bulk message deletion.

1. Wrong discord.js version

   ProblemThe code called v14 APIs on the installed v13, and every error was silently swallowed.

   FixMigrated to v14, with Node tests run against the real discord.js in CI.

2. Quota bypassable by URL

   ProblemThe Free plan limit only existed in the UI.

   FixServer-side check, before authorisation and on the OAuth return.

3. Bot never restarted

   ProblemCarbon 3 returns a signed difference: a disconnected bot appeared to have been offline for a negative duration.

   FixDifference computed the right way round, covered by a test.

4. Blocking sleep()

   ProblemA plugin could hold a PHP worker for up to five minutes.

   FixDelayed sends handed to a queued job.

5. Tickets never saved

   ProblemThe table pointed to a table dropped during the redesign.

   FixForeign key fixed and new registration routes.

1. October 2025 First commit, marketplace plan
2. January 2026 From 20 to 6 plugins, centralised logs
3. February 2026 ADR 001: single platform bot
4. February 2026 Free and Pro plans with Stripe
5. April 2026 Docker Compose stack
6. September 2026 Migration to discord.js 14

877

commits

146

migrations

35

bot action types

~800

PHP tests

Taken from the project’s source code and Git history on 8 October 2026. No usage or revenue figures are published.