aeStatusPage/.env.example
jmcqueen 007086caf6 Initial commit: status-page bridge with Webex bot management
Bridges third-party status pages into Webex spaces via RSS polling and
inbound webhooks (Statuspage / Status.io / Uptime Kuma / generic).

Includes an interactive Webex bot (websocket transport) that lets space
members register sources with an Adaptive Card instead of hand-editing
config/feeds.json: help, add, list, webhook <key>, remove <key>.

Ships with an atomic JSON store (per-file mutex, tmp+rename), parallel
RSS polling, and unit tests via node:test. All secrets are sourced from
environment variables (see .env.example); no credentials in the repo.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-08 16:08:34 -04:00

23 lines
792 B
Text

# Copy this file to `.env` and fill in the real values.
# Docker: pass with `--env-file .env` or via your orchestrator's secret store.
# --- Required ---
# Webex bot bearer token. Rotate at https://developer.webex.com if this value
# has ever been committed.
WEBEX_BOT_TOKEN=
# --- Optional ---
# Public base URL of this service, used only so the bot can show users the
# exact inbound webhook URL to configure in their status provider.
# Example: https://status-bridge.example.com
#PUBLIC_BASE_URL=
# Override server bind (config.json values are used if these are unset).
#SERVER_PORT=1449
#SERVER_NAME=aeStatusPage
# Disable the interactive Webex chat bot (leaving inbound status webhooks
# active). Any value other than 'true' (case-insensitive) turns the bot off.
#BOT_ENABLED=true