.env.example

# MeshCore Analyzer — Environment Configuration
# Copy to .env and customize. All values have sensible defaults.
#
# This file is read by BOTH docker compose AND manage.sh — one source of truth.
# manage.sh setup negotiates and updates only these production managed keys:
#   PROD_DATA_DIR, PROD_HTTP_PORT, PROD_HTTPS_PORT, PROD_MQTT_PORT, DISABLE_MOSQUITTO
# Each environment keeps config + data together in one directory:
#   ~/meshcore-data/config.json, meshcore.db, Caddyfile, theme.json
#   ~/meshcore-staging-data/config.json, meshcore.db, Caddyfile

# --- Production ---
# Data directory (database, theme, etc.)
# Default: ~/meshcore-data
# Used by: docker compose, manage.sh
PROD_DATA_DIR=~/meshcore-data

# HTTP port for web UI
# Default: 80
# Used by: docker compose
PROD_HTTP_PORT=80

# HTTPS port for web UI (TLS via Caddy)
# Default: 443
# Used by: docker compose
PROD_HTTPS_PORT=443

# MQTT port for observer connections
# Default: 1883
# Used by: docker compose
PROD_MQTT_PORT=1883

# Disable internal Mosquitto broker (set true to use external MQTT only)
# Default: false
# Used by: manage.sh + docker compose overrides
DISABLE_MOSQUITTO=false

# --- Staging (HTTP only, no HTTPS) ---
# Data directory
# Default: ~/meshcore-staging-data
# Used by: docker compose
STAGING_DATA_DIR=~/meshcore-staging-data

# HTTP port
# Default: 82
# Used by: docker compose
STAGING_GO_HTTP_PORT=82

# MQTT port
# Default: 1885
# Used by: docker compose
STAGING_GO_MQTT_PORT=1885