`README.md`

33 lines
# tools.designerwallcoverings.com — DW Tools Hub

One launcher page for every Designer Wallcoverings build tool, with a live up/down
status dot per tool. Zero dependencies (Node built-ins only).

## Run locally
```bash
node server.js            # OS-assigned free port, basic-auth admin/DW2024!
PORT=9815 node server.js  # fixed port
```
- `/`         launcher UI (auth)
- `/api/tools`  the manifest (auth)
- `/api/status` live TCP probe of every tool's port (auth)
- `/healthz`  open, unauthenticated 200 (fleet keepalive)

## The tools
All entries live in `tools.json` — add/edit a tool = a data edit, no code change.
Each tool is a **separate app** under `~/Projects/Designer-Wallcoverings/DW-Programming/`
on its own port; this hub just links to them and probes whether they're running.

Named ones: **150 DPI + Spoonflower flow** (150dpi), **Duplicate & Recolor / color
replacement / art coordinates** (v1.4/v1.3/v1), **Search by Color Wheel**, room-setting
tools, SKU importer, the vendor taggers, and the vendor updater dashboards.

## Status probe host
`PROBE_HOST` (default `127.0.0.1`) is where the tool apps listen. On Mac2 that's
localhost. If the hub goes public on Kamatera, set `PROBE_HOST` to the tailnet host
(Mac2) so the dots reflect the real app state, or deploy the tools alongside.

## Go-live (GATED)
Public `tools.designerwallcoverings.com` needs DNS (Cloudflare) + Kamatera deploy —
both Steve-gated. See `pending-approval/` memo. Note the DW CF zone is at its 200-record cap.