grabowski
6ae67dec63
CI / Format & lint (push) Successful in 22s
CI / Test suite (push) Successful in 59s
Docs / Validate documentation (push) Successful in 25s
Rust / fmt, clippy, test, build (push) Successful in 10m2s
Security / Dependency vulnerabilities (push) Successful in 2m11s
Security / Static analysis (push) Successful in 22s
Security / License report (push) Successful in 1m37s
Phase 2b/2c of docs/RUST_REWRITE.md. With FORECAST_IN_COLLECTOR=true (shared .env) ping-collector, after each cycle that brought newer RID or HII readings and at least hourly: loads the last 336 h (RID + HII mirror fill), fetches the rain forecast, runs every exported model (rust/forecast), stores forecast_history and forecast_current, and sends the ntfy notifications. The Python API then serves forecast_current as /forecast (computing in-process only when it is older than FORECAST_MAX_AGE_SECONDS) and neither forecasts nor notifies. ntfy (collector/src/notify.rs): a port of src/notify.py with the same topics, texts, hysteresis, capacity guard and notification_state keys, checked word for word on 751 messages generated by Python (testdata/gen_notify_cases.py). The change: for stations whose ThaiWater twin is the same sensor, a reading newer than RID's drives the level alerts (marked as ThaiWater telemetry), and the feed counts as stale only when neither source has a reading for 3 h. RID alone lagging is reported once after RID_STALE_ALERT_HOURS (18). This ends the nightly "gauge feed stale" / "recovered" pairs caused by RID's late reports. Commands: `forecast [--json] [--save] [--now] [--rain-file]`, `notify --dry-run`. scripts/forecast_parity.py compares Python and the collector on the live database (same moment, same rain); locally 48/48 rows identical. install_collector.sh: models export + that check on every install, --cutover-forecast (refuses on a failed check) and --rollback-forecast. Trees are packed into 24-byte nodes: 70 MB peak with all 15 models (was 140). Forecast values are written to NUMERIC as shortest round-trip text, so they round as psycopg2's do. DB test schemas get a counter (parallel tests collided on Windows' coarse clock).
133 lines
4.0 KiB
Bash
133 lines
4.0 KiB
Bash
# Northern Thailand Ping River Monitor Configuration
|
|
# Copy this file to .env and customize for your environment
|
|
|
|
# Database Configuration
|
|
DB_TYPE=postgresql
|
|
# Options: sqlite, mysql, postgresql, influxdb, victoriametrics
|
|
|
|
# SQLite Configuration (default)
|
|
WATER_DB_PATH=water_levels.db
|
|
|
|
# VictoriaMetrics Configuration
|
|
VM_HOST=localhost
|
|
VM_PORT=8428
|
|
VM_URL=
|
|
|
|
# InfluxDB Configuration
|
|
INFLUX_HOST=localhost
|
|
INFLUX_PORT=8086
|
|
INFLUX_DATABASE=ping_river_monitoring
|
|
INFLUX_USERNAME=
|
|
INFLUX_PASSWORD=
|
|
|
|
# PostgreSQL Configuration (Remote Server)
|
|
# Option 1: Full connection string (URL encode special characters in password)
|
|
POSTGRES_CONNECTION_STRING=postgresql://username:url_encoded_password@your-postgres-host:5432/water_monitoring
|
|
|
|
# Option 2: Individual components (password will be automatically URL encoded)
|
|
POSTGRES_HOST=your-postgres-host
|
|
POSTGRES_PORT=5432
|
|
POSTGRES_DB=water_monitoring
|
|
POSTGRES_USER=username
|
|
POSTGRES_PASSWORD=your:password@with!special#chars
|
|
|
|
# Examples for connection string:
|
|
# - Local: postgresql://postgres:password@localhost:5432/water_monitoring
|
|
# - Remote: postgresql://user:pass@192.168.1.100:5432/water_monitoring
|
|
# - With special chars: postgresql://user:my%3Apass%40word@host:5432/db
|
|
# - With SSL: postgresql://user:pass@host:port/db?sslmode=require
|
|
# - Connection pooling: postgresql://user:pass@host:port/db?pool_size=20&max_overflow=0
|
|
|
|
# Special character URL encoding:
|
|
# : → %3A @ → %40 # → %23 ? → %3F & → %26 / → %2F % → %25
|
|
|
|
# MySQL Configuration
|
|
MYSQL_CONNECTION_STRING=mysql://user:password@localhost:3306/ping_river_monitoring
|
|
|
|
# API Configuration
|
|
API_HOST=0.0.0.0
|
|
API_PORT=8000
|
|
API_WORKERS=1
|
|
# Public ThaiWater API key used to add Ping-basin water-level sensors.
|
|
THAIWATER_API_KEY=
|
|
|
|
# Data Collection Settings
|
|
SCRAPING_INTERVAL_HOURS=1
|
|
# RID poll minute past the hour; retry interval while RID is behind
|
|
RID_POLL_OFFSET_MINUTES=5
|
|
RID_RETRY_MINUTES=10
|
|
# Days of RID holes the leader re-fetches at startup (0 = off)
|
|
GAP_FILL_DAYS_ON_START=14
|
|
# false when the Rust ping-collector service collects (rust/collector);
|
|
# share the status file between both services for /scraping/status
|
|
COLLECTION_ENABLED=true
|
|
# SCRAPING_STATUS_FILE=/opt/thailand-water-monitor/collector-status.json
|
|
# true: ping-collector also forecasts (models/flood_*.json.gz, rust/forecast)
|
|
# and sends the ntfy notifications; this app serves its stored forecast and
|
|
# computes itself only when that is older than FORECAST_MAX_AGE_SECONDS.
|
|
# Set by scripts/install_collector.sh --cutover-forecast.
|
|
FORECAST_IN_COLLECTOR=false
|
|
# FORECAST_MAX_AGE_SECONDS=7200
|
|
# MODELS_DIR=models
|
|
REQUEST_TIMEOUT=30
|
|
MAX_RETRIES=3
|
|
RETRY_DELAY_SECONDS=60
|
|
|
|
# Data Retention
|
|
DATA_RETENTION_DAYS=365
|
|
|
|
# Logging Configuration
|
|
LOG_LEVEL=INFO
|
|
LOG_FILE=water_monitor.log
|
|
|
|
# Security (for production)
|
|
SECRET_KEY=your-secret-key-here
|
|
API_KEY=your-api-key-here
|
|
|
|
# Monitoring
|
|
ENABLE_METRICS=true
|
|
ENABLE_HEALTH_CHECKS=true
|
|
|
|
# Geographic Settings
|
|
TIMEZONE=Asia/Bangkok
|
|
DEFAULT_LATITUDE=18.7875
|
|
DEFAULT_LONGITUDE=99.0045
|
|
|
|
# External Services
|
|
NOTIFICATION_EMAIL=
|
|
SMTP_SERVER=
|
|
SMTP_PORT=587
|
|
SMTP_USERNAME=
|
|
SMTP_PASSWORD=
|
|
|
|
# Public push notifications via self-hosted ntfy (https://ntfy.sh, single binary).
|
|
# Leave NTFY_SERVER empty to disable. Topics published: <prefix>-<station>-warning,
|
|
# <prefix>-<station>-danger, <prefix>-warning, <prefix>-danger, <prefix>-p1-outlook,
|
|
# <prefix>-status. See docs/NOTIFICATIONS.md.
|
|
NTFY_SERVER=
|
|
# Where the monitor POSTs (defaults to NTFY_SERVER). Use the local ntfy
|
|
# address (loopback or Tailscale IP) so publishing does not depend on
|
|
# DNS / the reverse proxy being up.
|
|
NTFY_PUBLISH_URL=
|
|
NTFY_TOPIC_PREFIX=ping
|
|
NTFY_TOKEN=
|
|
PUBLIC_URL=https://water.buildfor.life/
|
|
# ping-collector notifier: report RID lagging this many hours while ThaiWater
|
|
# telemetry is current (0 = never)
|
|
RID_STALE_ALERT_HOURS=18
|
|
|
|
# Matrix Alerting Configuration
|
|
MATRIX_HOMESERVER=https://matrix.org
|
|
MATRIX_ACCESS_TOKEN=
|
|
MATRIX_ROOM_ID=
|
|
|
|
# Grafana Integration
|
|
GRAFANA_URL=http://localhost:3000
|
|
|
|
# Alert Configuration
|
|
ALERT_MAX_AGE_HOURS=2
|
|
ALERT_CHECK_INTERVAL_MINUTES=15
|
|
|
|
# Development Settings
|
|
DEBUG=false
|
|
DEVELOPMENT_MODE=false |