kianiadee/fleetops
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
18 commits 3 branches 0 tags 531 KiB
HTML 95.5%
Dockerfile 2.9%
JavaScript 1.6%
Find a file
david kiania a32735bca3 feat(tickets map): fan out co-located pins so faded-closed is visible 
Cluster-centroid tickets share an exact coordinate, so the open layer sat on
top of the faded closed pins (23 of 25 closed points were occluded) — the new
closed colouring was correct but invisible. Now pins sharing a coordinate are
fanned into a small deterministic sunflower spiral around it, computed across
BOTH layers so an open and a closed ticket at the same centroid separate.
Active (vivid) and closed (faded) now both show. Also default the Closed layer
on. Offsets are cosmetic (cluster centroids are already approximate).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-18 17:04:06 +03:00
docs feat(tickets): replace INC/CRQ map with INC operations dashboard 2026-06-16 11:42:23 +03:00
src feat(tickets map): fan out co-located pins so faded-closed is visible 2026-06-18 17:04:06 +03:00
.dockerignore feat: FleetOps analytics SPA (Caddy) — initial scaffold 2026-06-10 13:00:31 +03:00
.gitignore feat: FleetOps analytics SPA (Caddy) — initial scaffold 2026-06-10 13:00:31 +03:00
Caddyfile fix(caddy): evaluate {{env}} in env.js (templates mime) 2026-06-10 13:23:26 +03:00
Dockerfile feat: FleetOps analytics SPA (Caddy) — initial scaffold 2026-06-10 13:00:31 +03:00
README.md feat: FleetOps analytics SPA (Caddy) — initial scaffold 2026-06-10 13:00:31 +03:00

README.md

FleetOps

Fleet operations analytics for the Tracksolid fleet — fuel, utilisation, distance and driver behaviour. Sibling to FleetNow (live tracking); reuses the same warm-dark ops palette so the two feel like one product.

This is a self-contained single-page app (src/index.html, inline CSS/JS + Chart.js from CDN) served by Caddy. It reads the FleetOps analytics API (the dashboard_api /analytics/* endpoints).

Architecture

fleetops.fivetitude.com   (staging)  ─┐
fleetops.rahamafresh.com  (prod)      ─┼─► this SPA (Caddy :80, behind Traefik/Coolify)
                                        └─► API_BASE → dashboard_api /analytics/*
  • Web server: Caddy. Traefik (via Coolify) terminates TLS, so Caddy is a plain :80 file server. See Caddyfile.
  • Per-environment API base: Caddy's templates directive renders {{env "API_BASE"}} into /env.js at request time, so the same image serves staging and prod — just set the API_BASE env var on each Coolify app:
    • staging → https://fleetapi.fivetitude.com
    • prod → https://fleetapi.rahamafresh.com
    • if unset, index.html falls back to the staging API.

Endpoints consumed

Endpoint Panel
GET /analytics/filters cost-centre / city dropdowns
GET /analytics/fleet-summary KPI strip + per-vehicle table
GET /analytics/utilisation distance & idle daily-trend chart
GET /analytics/driver-behaviour driver leaderboard
GET /analytics/fuel fuel panel (data-gated)

The SPA's origin must be in the API's DASHBOARD_CORS_ORIGINS (staging API already allows fleetops.fivetitude.com).

Deploy

Coolify app (Dockerfile → Caddy), one per environment, bound to a branch:

Env Domain Branch API_BASE
staging fleetops.fivetitude.com staging https://fleetapi.fivetitude.com
prod fleetops.rahamafresh.com main https://fleetapi.rahamafresh.com

Promotion: feature → staging (auto-deploys staging via Forgejo webhook) → main (auto-deploys prod).

Local

docker build -t fleetops . && docker run --rm -p 8080:80 -e API_BASE=https://fleetapi.fivetitude.com fleetops
# open http://localhost:8080  (live data needs the localhost origin in the API CORS allowlist)