Pulse/.env.example
Pulse Monitor e386a83778 cleanup: remove legacy POLLING_INTERVAL env variable (addresses #447)
PVE polling is hardcoded to 10s since Proxmox cluster/resources endpoint only updates every 10s internally. Setting faster polling intervals was wasteful and provided no benefit.

Removed:
- POLLING_INTERVAL env variable and all references
- pollingInterval from config structs and API responses
- UI settings for polling interval (already removed)
- Dynamic polling interval updates via SIGHUP
- Legacy persistence code for saving polling settings

The monitoring loop now uses a hardcoded 10s interval matching Proxmox's update frequency.
2025-09-11 12:33:44 +00:00

33 lines
No EOL
1,017 B
Text

# Pulse Environment Variables - DEPLOYMENT OVERRIDES ONLY
# These override UI settings. Most users should configure via the web UI instead.
#
# For systemd: Copy to /etc/pulse/.env or use 'systemctl edit pulse-backend'
# For Docker: Use -e flags or docker-compose environment section
#
# WARNING: Do NOT put passwords, API tokens, or other secrets in .env files!
# Server Configuration
FRONTEND_PORT=7655
# BACKEND_HOST=0.0.0.0
# CORS Settings (for reverse proxy setups)
# ALLOWED_ORIGINS=*
# Updates
# UPDATE_CHANNEL=stable # Options: stable, rc
# AUTO_UPDATE_ENABLED=false # Enable automatic updates
# AUTO_UPDATE_CHECK_INTERVAL=24 # Hours between update checks
# AUTO_UPDATE_TIME=03:00 # Time to apply updates (HH:MM format)
# Monitoring
# Note: PVE polling is hardcoded to 10s (Proxmox cluster/resources updates every 10s)
# CONNECTION_TIMEOUT=10
# Logging
# LOG_LEVEL=info
# LOG_MAX_SIZE=100
# LOG_MAX_AGE=30
# Data Storage
# PULSE_DATA_DIR=/etc/pulse
# METRICS_RETENTION_DAYS=7