Public Web Surface

Only the public signal is exposed to browsers.

RealBot now has a focused website layer with a branded front end while the bot commands, handlers, assets, and secrets stay server-side. The public surface stays intentionally narrow, but it no longer looks generic.

Browse leaderboards Open dashboard Open health JSON View route map

RealBot identity

Chrome lettering, electric blue thrust, magenta edge glow, and the bot core at center now drive the public site palette.

Live Runtime

Server status

Status Checking...
Uptime Checking...
Timestamp Checking...

Public vs Private

What changed

Public at runtime

  • Realest/public/* static files
  • /dashboard for bot runtime stats
  • /leaderboards for public leaderboard views
  • /api/health for status checks
  • /api/bot/* for Discord-backed web data
  • /api/leaderboards* for public leaderboard data
  • /api/meta for a small route map

Private at runtime

  • commands/, events/, handlers/
  • assets/, utils/, prefixCommands/
  • .env and bot-only startup code

Layout

Cleaner project split

Realest/
  bot/        # Discord runtime bootstrap
  public/     # Browser-facing website files
  web/        # Static server and web routes
  commands/
  events/
  handlers/
  utils/

Important

Runtime privacy is not repo privacy

If you make the GitHub repo public, every tracked source file is still public in the repository. The public folder only controls what the running website exposes.