Files
pulse/.env.example
T

47 lines
1.6 KiB
Bash

# ProxMox Node Configuration
# Replace with your ProxMox node details
# Node 1
PROXMOX_NODE_1_NAME=Proxmox Node 1
PROXMOX_NODE_1_HOST=https://proxmox.local:8006
PROXMOX_NODE_1_TOKEN_ID=root@pam!pulse
PROXMOX_NODE_1_TOKEN_SECRET=your-token-secret
# Node 2 (optional)
PROXMOX_NODE_2_NAME=Proxmox Node 2
PROXMOX_NODE_2_HOST=https://proxmox2.local:8006
PROXMOX_NODE_2_TOKEN_ID=root@pam!pulse
PROXMOX_NODE_2_TOKEN_SECRET=your-token-secret
# App Configuration
PORT=7654
# Frontend Configuration
# This ensures the frontend connects to the backend using IPv4 instead of IPv6
# Important: Use 127.0.0.1 (IPv4) instead of ::1 (IPv6) to avoid connection issues
VITE_API_URL=http://127.0.0.1:7654
# Environment Configuration
# Note: When using start-dev.sh for development, it will automatically set NODE_ENV=development
# These settings primarily apply to Docker/production deployments
NODE_ENV=production
LOG_LEVEL=info # Options: error, warn, info, debug
ENABLE_DEV_TOOLS=false # Set to true only for debugging production issues
METRICS_HISTORY_MINUTES=60 # How many minutes of metrics history to keep in memory
# Mock Data Configuration
# Set to false to connect to real Proxmox nodes
USE_MOCK_DATA=false
MOCK_DATA_ENABLED=false
# SSL Configuration
# SECURITY WARNING:
# - For development or internal networks, you can set these to true/0
# - For production, set these to false/1 and ensure proper SSL certificates are installed
# - Setting these to true/0 disables SSL certificate validation and is not secure for production
IGNORE_SSL_ERRORS=true
NODE_TLS_REJECT_UNAUTHORIZED=0
# Polling Intervals (in milliseconds)
NODE_POLLING_INTERVAL_MS=1000
EVENT_POLLING_INTERVAL_MS=1000