Files
lighting-controller/.env.example
Pi User aa9f892454 Add CONTROL_SERVER_HOST to allow external connections
- Add CONTROL_SERVER_HOST environment variable (default: 0.0.0.0)
- Server now binds to all interfaces by default for external access
- Update .env and .env.example with new host configuration
- Allows UI clients to connect from other machines on the network
2025-10-03 20:24:20 +13:00

46 lines
1.3 KiB
Plaintext

# Lighting Controller Configuration
# ==============================
# WebSocket Configuration
# ==============================
# WebSocket URI for the control server
# Used by UI client and test scripts to connect to the control server
#
# Default: Use wlan0 IP for remote connections
CONTROL_SERVER_URI=ws://10.42.0.1:8765
#
# For local development (running on same machine as control server):
# CONTROL_SERVER_URI=ws://localhost:8765
#
# For custom IP (if your Pi has a different address):
# CONTROL_SERVER_URI=ws://YOUR_PI_IP:8765
# Control server WebSocket host (bind address)
# 0.0.0.0 = listen on all interfaces (allows external connections)
# localhost or 127.0.0.1 = listen only on localhost (local only)
CONTROL_SERVER_HOST=0.0.0.0
# Control server WebSocket port
CONTROL_SERVER_PORT=8765
# ==============================
# Transport Configuration
# ==============================
# Transport method for LED communication
# Options: spi, websocket
TRANSPORT=spi
# ==============================
# Sound Detection Configuration
# ==============================
# Audio input device index (use sound.py to list available devices)
AUDIO_INPUT_DEVICE=1
# MIDI TCP configuration
MIDI_TCP_HOST=127.0.0.1
MIDI_TCP_PORT=65432
# Sound control server configuration
SOUND_CONTROL_HOST=127.0.0.1
SOUND_CONTROL_PORT=65433