feat(printing): spec Obico ML failure detection (ml_api only) #14

Open
adam wants to merge 1 commit from feat/obico-ml-detection into main
Owner

Specs self-hosted Obico ML failure detection for the printing stack (ml_api service only — Bambuddy handles camera sampling/smoothing/action, so the full Obico web/tasks/redis server isn't needed).

Changes

  • docs/plans/obico-ml-detection.md — feasibility + architecture, endpoint contract (GET /p/?img= :3333), CPU-only rationale, image-source decision, deploy mechanics
  • stacks/printing — add obico-ml service (dockernet, 3333:3333) + OBICO_ML_IMAGE var in .env; Bambuddy (host-net) reaches it at http://192.168.4.200:3333

Not deployed. printing has autoUpdate:false / no webhook, so this needs a manual Dockhand sync (break-glass) plus building the image first.

🤖 Generated with Claude Code

Specs self-hosted Obico ML failure detection for the printing stack (ml_api service only — Bambuddy handles camera sampling/smoothing/action, so the full Obico web/tasks/redis server isn't needed). **Changes** - `docs/plans/obico-ml-detection.md` — feasibility + architecture, endpoint contract (`GET /p/?img=` :3333), CPU-only rationale, image-source decision, deploy mechanics - `stacks/printing` — add `obico-ml` service (dockernet, `3333:3333`) + `OBICO_ML_IMAGE` var in `.env`; Bambuddy (host-net) reaches it at `http://192.168.4.200:3333` **Not deployed.** `printing` has `autoUpdate:false` / no webhook, so this needs a manual Dockhand sync (break-glass) plus building the image first. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Wire Bambuddy's built-in Obico integration to a self-hosted detection
endpoint after a spaghetti print failure. Bambuddy is the command center
and does its own camera sampling + smoothing + action, so only Obico's
ml_api service is needed — not the full web/tasks/redis server.

- docs/plans/obico-ml-detection.md: feasibility + architecture, endpoint
  contract (GET /p/?img= :3333), CPU-only rationale, image-source decision
  (build on crucible→Forgejo vs stale Docker Hub image), deploy mechanics
- stacks/printing: add obico-ml service (dockernet, 3333:3333) + OBICO_ML_IMAGE
  var in .env; Bambuddy (host-net) reaches it at http://192.168.4.200:3333

Not deployed — printing has autoUpdate:false / no webhook, so this needs a
manual Dockhand sync (break-glass) plus building the image first.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/obico-ml-detection:feat/obico-ml-detection
git switch feat/obico-ml-detection

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff feat/obico-ml-detection
git switch feat/obico-ml-detection
git rebase main
git switch main
git merge --ff-only feat/obico-ml-detection
git switch feat/obico-ml-detection
git rebase main
git switch main
git merge --no-ff feat/obico-ml-detection
git switch main
git merge --squash feat/obico-ml-detection
git switch main
git merge --ff-only feat/obico-ml-detection
git switch main
git merge feat/obico-ml-detection
git push origin main
Sign in to join this conversation.
No reviewers
No labels
lab-honing
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
adam/foundry!14
No description provided.