gorkem-bwl
705c19f7c8
Deployments with restricted egress could not run checks at all: got does not read HTTP_PROXY/HTTPS_PROXY (unlike curl or axios), and NODE_USE_ENV_PROXY only affects Node's built-in fetch, which got does not use. Even a correctly built proxy agent was discarded, because HttpProvider overwrote options.agent on every request. Proxy selection is resolved per check and applied where the agent is chosen. NO_PROXY handling is delegated to proxy-from-env rather than reimplemented, so wildcards, host lists and port-qualified entries behave exactly as operators expect from curl. Infrastructure monitors are excluded by default. Hardware and pagespeed checks both delegate to HttpProvider, so a naive global proxy would also capture Capture agents — which normally sit on the internal network, where proxying them fails or hairpins. PROXY_MONITOR_TYPES is the escape hatch for deployments whose agents genuinely are behind the proxy, and accepts "none" to disable proxying without unsetting the environment variables. Values that are not real monitor types, or that open raw sockets and cannot be proxied (ping, port, docker, grpc, websocket, dns, game), are dropped and logged so a typo cannot silently disable proxying. Agents are cached by proxy URL and TLS mode. Keying on TLS matters: sharing one agent between a strict monitor and an ignoreTlsErrors monitor would leak the relaxed setting across monitors. Caching also preserves pooling, so 50 monitors share tunnels instead of dialling the proxy per check. Both new dependencies were already present transitively (76K total). Notification providers still call out directly and are unaffected; that is a known follow-up for the same class of deployment.
54 lines
1.7 KiB
Bash
54 lines
1.7 KiB
Bash
# ==============================================
|
|
# Checkmate Server Configuration
|
|
# ==============================================
|
|
# Copy this file to .env and fill in your values
|
|
|
|
# Server Configuration
|
|
# --------------------
|
|
NODE_ENV=development
|
|
LOG_LEVEL=debug
|
|
|
|
# Database
|
|
# --------
|
|
DB_CONNECTION_STRING=mongodb://localhost:27017/uptime_db
|
|
QUEUE_MODE="primary"
|
|
QUEUE_PRIMARY_PROCESSES="true"
|
|
|
|
# JWT Authentication
|
|
# ------------------
|
|
JWT_SECRET=my_secret
|
|
TOKEN_TTL=99d
|
|
|
|
# Client Configuration
|
|
# --------------------
|
|
CLIENT_HOST=http://localhost:5173
|
|
|
|
# Optional Configuration
|
|
# ----------------------
|
|
ORIGIN=localhost
|
|
|
|
# Feature Flags
|
|
# -------------
|
|
# Set to "false" to disable the selectable theme feature on status pages.
|
|
# When disabled, all status pages render with the default "refined" theme.
|
|
STATUS_PAGE_THEMES_ENABLED=true
|
|
|
|
# Outbound Proxy
|
|
# --------------
|
|
# Route monitor checks through an HTTP proxy, for deployments whose egress is
|
|
# restricted. Credentials may be embedded: http://user:pass@proxy:3128
|
|
# HTTP_PROXY=http://proxy.corp.example:3128
|
|
# HTTPS_PROXY=http://proxy.corp.example:3128
|
|
#
|
|
# Hosts that must be reached directly. Supports wildcards and host lists, with
|
|
# the same semantics curl uses.
|
|
# NO_PROXY=localhost,127.0.0.1,*.internal,10.0.0.5
|
|
#
|
|
# Monitor types to route through the proxy, comma-separated. Defaults to
|
|
# "http,pagespeed". Infrastructure ("hardware") monitors are excluded by
|
|
# default because Capture agents normally sit on the internal network — add it
|
|
# here if yours are reachable only through the proxy. Use "none" to disable
|
|
# proxying without unsetting the variables above. Types that open raw sockets
|
|
# (ping, port, docker, grpc, websocket, dns, game) cannot be proxied.
|
|
# PROXY_MONITOR_TYPES=http,pagespeed
|