Replace baked-in UOM/MysticMoon/UOMysticmoon branding with a BRAND_* env scheme so one prebuilt image runs as any shard; UOMysticmoon becomes the first tenant that sets these vars rather than a special case in the code. Architecture (chosen because the app ships as a prebuilt image): - server/src/config/brand.js + bot/src/brand.js read BRAND_* once at boot, with Runic Gateway defaults. - Text/colors reach the SPA at RUNTIME through the existing public settings API (settings.model.getPublic -> SiteContext), so no client rebuild. The admin-editable site title + contact email still override BRAND_NAME/email. - SiteContext applies BRAND_ACCENT_COLOR to the --accent CSS var at runtime. - Express templates the built index.html <title>/description/OG/favicon at serve time from BRAND_* (renderIndexHtml in app.js). - Server-side consumers read brand directly: emails, TOTP issuer, API docs, boot logs, HTML error page. Bot uses it for embed color + logs. Assets: logo/hero/favicon delivered from a ./brand:/app/brand bind-mount (BRAND_LOGO/HERO/FAVICON), with neutral defaults baked in; hero falls back to a built-in image when unset. Scope: also genericized package.json names (uomysticmoon-* -> runic-gateway-*) and the DB_NAME/DB_USER/COOKIE_NAME code defaults (runic_gateway/runic/ rg_token). Production keeps its real values by pinning them in .env — see .env.uomysticmoon.example, which reproduces the exact UOMysticmoon identity (proof the substitution works). Changing a deployed COOKIE_NAME invalidates existing sessions, so UOMysticmoon pins uomm_token. Verified: 193 server tests pass, client builds, app.js loads + templates the built index.html, brand transform injects title/description/OG/favicon.
46 lines
2.2 KiB
Plaintext
46 lines
2.2 KiB
Plaintext
# ─── Runic Gateway Discord bot — local dev environment ───
|
|
# Copy to bot/.env for running `npm run dev` outside Docker.
|
|
# (In Docker, the root .env / docker-compose provides these instead.)
|
|
#
|
|
# NOTE: there is no Discord bot token here on purpose. The token is entered
|
|
# in the admin panel (Discord Bot page), stored encrypted in the main site's
|
|
# DB, and pushed to this process in-memory over the internal API. It is
|
|
# never read from an env var and never written to this process's disk.
|
|
|
|
PORT=4100
|
|
|
|
# Logging — written to BOTH the console and a log file (default <bot>/logs/bot.log).
|
|
LOG_LEVEL=debug # console verbosity: error | warn | info | debug
|
|
FILE_LOG_LEVEL=debug # file verbosity
|
|
LOG_TO_FILE=true # set false for console-only
|
|
# LOG_DIR= # defaults to bot/logs
|
|
# LOG_FILE=bot.log
|
|
|
|
# Shared secret for the internal API between this bot and the main site
|
|
# (server/). MUST be byte-for-byte identical to BOT_INTERNAL_KEY in
|
|
# server/.env.example / the root .env.example — it is the only auth on both
|
|
# sides' /internal/* routes, so a mismatch silently breaks every server<->bot
|
|
# call with 401s. Generate one long random string and copy it to both places.
|
|
BOT_INTERNAL_KEY=dev-only-change-me-bot-key
|
|
|
|
# Where this bot calls back to the main site to fetch its config on boot
|
|
# (GET .../internal/bot-config), so a restart self-reconnects without needing
|
|
# the admin panel to push config again. This targets the site's UNPUBLISHED
|
|
# internal port (INTERNAL_PORT, default 3001) — NOT the public 3000. See #33.
|
|
SITE_INTERNAL_URL=http://localhost:3001/internal/bot-config
|
|
|
|
# Read-only PUBLIC API base (Phase 7) — no shared secret, same data any
|
|
# visitor's browser can fetch. Used by /wiki (search) and /announce
|
|
# (re-post an existing news item).
|
|
SITE_PUBLIC_URL=http://localhost:3000/api/v1/public
|
|
|
|
# Database (Phase 2+) — same physical DB as the main site, but the bot only
|
|
# ever reads/writes its OWN tables (guild_config, mod_actions, warnings, and
|
|
# more in later phases). It never touches site tables (users, bot_config,
|
|
# etc.) directly. Point this at the same DB the server/ uses.
|
|
DB_HOST=127.0.0.1
|
|
DB_PORT=3306
|
|
DB_NAME=runic_gateway
|
|
DB_USER=runic
|
|
DB_PASSWORD=change-me-db-password
|