mirror of
https://github.com/Kpa-clawbot/meshcore-analyzer.git
synced 2026-11-11 11:57:57 +00:00
Red commit: `7277ca23` ([failing CI](https://github.com/Kpa-clawbot/CoreScope/actions/runs/40190626951)). Fixes #2229. Management startup now defines logging helpers before normalizing CRLF environment files. Updates refresh version, revision and build time after checking out the target. Deployment verification and all five Compose healthchecks use `/api/healthz`, so an available statistics endpoint cannot report an unfinished startup as healthy. - The actual-script regression passes 15 checks: LF/CRLF/no environment file, repeat startup, all update targets, failed checkout, delayed/failed readiness, HTTPS readiness and unchanged informational statistics. - RED CI reproduced all 11 intended failures; GREEN `7ff9050b` passes the full standalone frontend suite and shell syntax checks. - Browser verified: an isolated Go fixture at http://127.0.0.1:18851 renders Home and returns ready=true from `/api/healthz`. - Git, Docker and network boundaries are mocked in management tests. No real container update was performed locally; CI validates the Compose/build path. - No new configuration, dependencies, schema changes or packet-processing work. Privacy, whitespace and scope checks passed. The external home-directory preflight bundle is unavailable; applicable checks were performed locally. Independent review found no outstanding fixes. [Final CI](https://github.com/Kpa-clawbot/CoreScope/actions/runs/40191647297) passed on `7ff9050b`, including all three browser shards and both architecture builds.
33 lines
1.2 KiB
YAML
33 lines
1.2 KiB
YAML
# CoreScope — simple single-container deployment using the pre-built
|
|
# image from GHCR.
|
|
#
|
|
# AUDIENCE: third-party operators running a self-hosted CoreScope on
|
|
# ONE host. Ships with the built-in Mosquitto broker DISABLED by
|
|
# default (DISABLE_MOSQUITTO defaults to `false` here, meaning
|
|
# mosquitto RUNS in-container — the historical shape); flip to `true`
|
|
# if you already have an external MQTT broker to point CoreScope at.
|
|
#
|
|
# For the CoreScope maintainers' internal staging deployment (with a
|
|
# standalone `mqtt-broker` container on external network
|
|
# `meshcore-net`), see `docker-compose.staging.yml`.
|
|
#
|
|
# Usage: docker compose -f docker-compose.example.yml up -d
|
|
# Docs: https://github.com/Kpa-clawbot/CoreScope/blob/master/DEPLOY.md
|
|
|
|
services:
|
|
corescope:
|
|
image: ghcr.io/kpa-clawbot/corescope:latest
|
|
ports:
|
|
- "${HTTP_PORT:-80}:80"
|
|
volumes:
|
|
- ${DATA_DIR:-./data}:/app/data
|
|
environment:
|
|
- DISABLE_CADDY=${DISABLE_CADDY:-true}
|
|
- DISABLE_MOSQUITTO=${DISABLE_MOSQUITTO:-false}
|
|
restart: unless-stopped
|
|
healthcheck:
|
|
test: ["CMD", "wget", "-qO-", "http://localhost:3000/api/healthz"]
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|