monster/modelbeast
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
232cc84420
modelbeast/web
History
MODELBEAST b8c333a93e Unified worker pool: gpu lane dispatches across M3 + M1 nodes (HANDOFF2 phase B) 
The gpu lane is now a NODE POOL (this Mac + remote workers from nodes.json) instead
of a single-Metal semaphore. A gpu job runs on whichever node is free:
- server/remote.py: ssh+rsync dispatch — mkdir remote dirs, rsync inputs out, run
  the operator's run.py over ssh with repo-relative paths (HF_TOKEN sourced from the
  node's .env.remote, off the process table), rsync outputs back, clean up. Cached
  health checks; per-node operator allowlist.
- runner: _acquire_gpu_node picks the first free node that supports the op (local
  runs anything; a remote must list it + be reachable → auto-fallback to local).
  _run_job branches local/remote; the M1 never touches the M3's DB.
- sysinfo/Dashboard: gpu lane limit = pool size; per-node status cards.
- nodes.json (gitignored, primary-only): M1 worker, allowlist excludes trellis_mac
  (bf16 unverified on M1) + brush_train (not installed there).

Verified: two FLUX jobs from one queue split M3(local, 10.3s) + M1(remote via ssh,
21.2s), both images rsync'd back and registered on the M3.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14 18:18:09 +10:00
..
public Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00
src Unified worker pool: gpu lane dispatches across M3 + M1 nodes (HANDOFF2 phase B) 2026-07-14 18:18:09 +10:00
.gitignore Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00
.oxlintrc.json Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00
index.html Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00
package-lock.json Phase 1 + framework: settings/secrets, queue lanes, job mgmt, inbox, 8 new operators 2026-07-12 21:42:27 +10:00
package.json Phase 1 + framework: settings/secrets, queue lanes, job mgmt, inbox, 8 new operators 2026-07-12 21:42:27 +10:00
README.md Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00
vite.config.js Phase 0 baseline: FastAPI+SQLite operator pipeline, React/three.js UI, ffprobe/ffmpeg_frames/blender_convert operators 2026-07-12 21:05:22 +10:00

README.md

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and Oxlint's TypeScript related rules in your project.