sites.json

[
  { "name": "portfolio",                "url": "https://www.aswincloud.com" },
  { "name": "blog",                     "url": "https://blog.aswincloud.com" },
  { "name": "status",                   "url": "https://status.aswincloud.com" },
  { "name": "resume",                   "url": "https://resume.aswincloud.com" },
  { "name": "ttperf",                   "url": "https://ttperf.aswincloud.com" },
  { "name": "ttnn-ops-coverage",        "url": "https://ttnn-ops-coverage.aswincloud.com" },
  { "name": "ttnn-eltwise-performance", "url": "https://ttnn-eltwise-performance.aswincloud.com" },
  { "name": "provision",                "url": "https://provision.aswincloud.com" },
  { "name": "auth-broker",              "url": "https://auth.aswincloud.com" },
  { "name": "shiptrack",                "url": "https://shiptrack.aswincloud.com" },
  { "name": "invoicer",                 "url": "https://invoicer.aswincloud.com" },
  { "name": "pr-reviewer",              "url": "https://pr-reviewer.aswincloud.com" },
  { "name": "chat",                     "url": "https://chat.aswincloud.com" },
  { "name": "support",                  "url": "https://support.aswincloud.com" },
  { "name": "3d-prints",                "url": "https://3d-prints.aswincloud.com" },
  {
    "name": "console",
    "url": "https://console.aswincloud.com",
    "expect": [302],
    "redirect_to": "aswincloud.cloudflareaccess.com",
    "note": "Cloudflare Access-gated. The 302 to the Access login page IS the healthy state — do not 'fix' this to 200. CAVEAT: Access answers at Cloudflare's EDGE, before the origin, so a green tick here only proves Cloudflare is up, not the app behind it."
  },

  {
    "name": "truenas",
    "url": "https://truenas.aswincloud.com/ui/",
    "expect": [200, 302],
    "redirect_to": "aswincloud.cloudflareaccess.com",
    "contains": "<base href=\"/ui/\">",
    "note": "Homelab NAS behind Cloudflare Access (verified via the Access API: app 'truenas', policies Allow-Domain / Allow-GitHub-Org / Bypass-Home-IP). Answers differ BY NETWORK: from the home IP the bypass applies and the real UI returns 200; from anywhere else — including GitHub runners — Access answers 302 to its login page. Both are healthy, so both are accepted, and each is verified: a 302 must point at the Access login, a 200 must carry the real <base> tag. The Angular SPA sends an EMPTY <title>, so <base> is the only stable needle. CAVEAT: the 302 comes from Cloudflare's EDGE, before the origin, so a runner's green tick does not prove the NAS itself is up."
  },
  {
    "name": "watch",
    "url": "https://watch.aswincloud.com/web/",
    "contains": "Jellyfin",
    "note": "Homelab Jellyfin. Root 302s to /web/, so probe /web/ directly."
  },
  {
    "name": "torrent",
    "url": "https://torrent.aswincloud.com",
    "contains": "qBittorrent",
    "note": "Homelab qBittorrent. Also watched every 30s by status.aswincloud.com — this is a slower backstop, not the primary monitor."
  }
]