Files
Pulse/docker-compose.yml
rcourtman 521d3a7c6e Fix docker-compose.yml temperature proxy bind mount configuration
This corrects several issues with the temperature proxy configuration
in the example docker-compose.yml:

Issues fixed:
1. **Wrong mount path**: Was using /mnt/pulse-proxy (LXC path) instead of
   /run/pulse-sensor-proxy (Docker path). While the client auto-detects both
   paths, this was inconsistent with documentation.

2. **Wrong permissions**: Was mounted as :ro (read-only) but needs :rw
   (read-write) for the Unix socket to work properly.

3. **Enabled by default**: Would cause container startup issues if the
   proxy wasn't installed on the host.

Changes:
- Commented out the bind mount by default (requires manual setup)
- Changed path from /mnt/pulse-proxy to /run/pulse-sensor-proxy
- Changed permissions from :ro to :rw
- Added clear comment explaining it requires setup with --standalone flag
- Points users to documentation

Now matches the documented Docker setup process and won't break
fresh installations where the proxy isn't installed yet.
2025-11-05 18:18:04 +00:00

27 lines
733 B
YAML

version: '3.8'
services:
pulse:
image: ${PULSE_IMAGE:-rcourtman/pulse:latest}
container_name: pulse
restart: unless-stopped
ports:
- "${PULSE_PORT:-7655}:7655"
volumes:
- pulse-data:/data
# Secure temperature monitoring via host-side proxy (requires setup - see docs)
# Uncomment after installing pulse-sensor-proxy on host with --standalone flag
# - /run/pulse-sensor-proxy:/run/pulse-sensor-proxy:rw
environment:
- TZ=${TZ:-UTC}
healthcheck:
test: ["CMD", "wget", "--quiet", "--tries=1", "--spider", "http://localhost:7655/api/health"]
interval: 30s
timeout: 10s
retries: 3
start_period: 10s
volumes:
pulse-data:
driver: local