kamilkrzywdaandOpenCode
25f99f04ad
CI / build + unit (pull_request) Successful in 46s
The MeshMonitor gateway uses a valid Let's Encrypt certificate, so standard TLS certificate verification already works — no workaround needed. The flag was a security downgrade: it disabled cert verification for ALL outbound connections in the container (including the LLM and opencode services), not just the gateway. - docker-compose.yml: drop NODE_TLS_REJECT_UNAUTHORIZED env line + comment - src/main.ts: drop process.env.NODE_TLS_REJECT_UNAUTHORIZED + comments - CHANGELOG.md: correct the v0.22.0 Docker bullet wording Part of the already-open MeshMonitor connection work (PR #56): no version bump, no new changelog section. Co-Authored-By: OpenCode <noreply@opencode.ai>
35 lines
1.2 KiB
YAML
35 lines
1.2 KiB
YAML
services:
|
|
bot:
|
|
build: .
|
|
environment:
|
|
TZ: Europe/Warsaw
|
|
MESHMONITOR_API_TOKEN: ${MESHMONITOR_API_TOKEN:-}
|
|
MESHMONITOR_API_BASE: ${MESHMONITOR_API_BASE:-https://meshmonitor.kkhost.pl/api/v1}
|
|
MESHMONITOR_SOURCE: ${MESHMONITOR_SOURCE:-default}
|
|
MESHMONITOR_TIMEOUT_MS: ${MESHMONITOR_TIMEOUT_MS:-15000}
|
|
MESH_DB_PATH: ./data/mesh-bot.db
|
|
MESH_POLL_MS: '1000'
|
|
MESH_NOTIFY_CHANNEL: '${MESH_NOTIFY_CHANNEL:-3}'
|
|
OPENCODE_API: ${OPENCODE_API:-http://172.24.0.1:9898}
|
|
OPENCODE_WORKSPACE_PATH: ${OPENCODE_WORKSPACE_PATH:-/home/krzyw/projects/sandbox/mesh-bot}
|
|
OPENCODE_SESSION: ${OPENCODE_SESSION:-}
|
|
OPENCODE_USER: ${OPENCODE_USER:-}
|
|
OPENCODE_PASS: ${OPENCODE_PASS:-}
|
|
WEATHER_CRON: ${WEATHER_CRON:-}
|
|
volumes:
|
|
- mesh_data:/app/data
|
|
restart: unless-stopped
|
|
networks:
|
|
- dev_net
|
|
labels:
|
|
- 'traefik.enable=true'
|
|
- 'traefik.http.routers.mesh-bot.rule=Host(`bot.dev.kkhost.pl`)'
|
|
- 'traefik.http.routers.mesh-bot.entrypoints=web'
|
|
- 'traefik.http.services.mesh-bot.loadbalancer.server.port=3000'
|
|
volumes:
|
|
mesh_data:
|
|
|
|
networks:
|
|
dev_net:
|
|
external: true
|