monoscope/.env.example at master · monoscope-tech/monoscope · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
DATABASE_URL="host=localhost user=postgres password=postgres dbname=monoscope port=5432 sslmode=disable"
PORT=8080
GRPC_PORT=4317
MIGRATIONS_DIR="./static/migrations/"
ENVIRONMENT=DEV
LOG_LEVEL=Trace
LOGGING_DESTINATION=StdOut

BASIC_AUTH_ENABLED=True
BASIC_AUTH_USERNAME=admin
BASIC_AUTH_PASSWORD=changeme

TEST_EMAIL=
API_KEY_ENCRYPTION_SECRET_KEY=monoscope123456monoscope12345678

SENDGRIDAPIKEY=
MIGRATE_AND_INITIALIZE_ON_START=True

SLACK_CLIENT_ID=
SLACK_CLIENT_SECRET=
SLACK_SIGNING_SECRET=
SLACK_APP_ID=
SLACK_REDIRECT_URI=https://app.monoscope.tech/slack/oauth/callback

ENABLE_PUBSUB_SERVICE=True

ENABLE_PUBSUB_SERVICE=True
ENABLE_BACKGROUND_JOBS=True
POSTMARK_TOKEN=
ENABLE_BROWSER_MONITORING=False

# Optional Twilio Content Template SID (HX + 32 hex digits) used for both
# query-monitor alerts and recoveries. An invalid configured SID prevents startup.
# Variables: 1 project, 2 monitor title, 3 Alerting/Recovered, 4 monitor or issue URL.
WHATSAPP_MONITOR_TEMPLATE=

# GitHub App integration (repositories, source context, PR reviews, dashboard sync)
# See docs/plans/2026-09-30-pr-impact-review.md for setup instructions.
GITHUB_APP_ID=
GITHUB_APP_NAME=monoscope
GITHUB_APP_WEBHOOK_SECRET=
GITHUB_APP_PRIVATE_KEY=
# User authorization credentials from the same GitHub App registration.
GITHUB_CLIENT_ID=
GITHUB_CLIENT_SECRET=

GH_TEST_PAT="ghp_your_token"
GH_TEST_OWNER="monoscope-tech"
GH_TEST_REPO="monoscope-sync-test"

CYPRESS_RECORD_KEY=

FONTAWESOME_PRO_TOKEN=your_pro_kit_token_here

# --- Live Tail -------------------------------------------------------------
# Streams matching logs to the browser over SSE, matched on the ingest pod before the
# TimeFusion/Postgres write. No configuration: it is on, and it works with or without Kafka.
#
# Transport is derived from KAFKA_BROKERS, which you already set:
#   brokers configured  -> the `live_tail` Kafka topic (create it with short retention:
#                          rpk topic create live_tail -p 6 -r 1 \
#                            -c retention.ms=600000 -c retention.bytes=67108864)
#   no brokers          -> the projects.live_tail_events relay table, so a deployment
#                          without Kafka still gets a working tail and needs no new
#                          infrastructure.
#
# Everything else (lease length, queue depths, per-user and per-project caps) is a constant
# in Pkg.LiveTail — none of it is a deployment decision.

# ---------------------------------------------------------------------------
# Local deploy (`make ship`) — not read by the server, only by scripts/ci/ci.sh.
#
# Use the per-app DEPLOY TOKEN (CapRover → your app → Deployment), not the admin
# password: it deploys that one app and can be rotated on its own. The password
# is optional and only `make deploy-status` uses it, so the credential that sits
# in every developer's .env is the one that cannot enumerate the server.
# ---------------------------------------------------------------------------
# CAPROVER_URL=https://captain.example.com
# CAPROVER_APP=monoscope
# CAPROVER_APP_TOKEN=
# CAPROVER_PASSWORD=