2.4 KiB
2.4 KiB
type, status, source, repo, repo_url, language, branch, tags, updated
| type | status | source | repo | repo_url | language | branch | tags | updated | ||
|---|---|---|---|---|---|---|---|---|---|---|
| project | active | git.alwisp.com | jason/mrp-qrcode | https://git.alwisp.com/jason/mrp-qrcode | TypeScript | main |
|
2026-05-29 |
mrp-qrcode
Repository: jason/mrp-qrcode · branch main · TypeScript
Summary
MRP QR Code System — fabrication shop tracker with printable QR traveler cards, phone-based operator scan flow, PDF generation, and in-browser STEP viewer
Current status
Active. Synced from Gitea on 2026-05-29.
Documentation overview
MRP QR Code System
A single-container, self-hosted Manufacturing Resource Planning (MRP) app built around printable QR-coded traveler cards. Designed for small fabrication shops running on an Unraid server with phone-based operators.
Status
Shipped (see docs/BUILD-PLAN.md): steps 1, 2, 3, 4, 5, 6, 8.
- 1. Scaffold + auth (admin email/password, operator name/4-digit PIN with 12 h device session, PIN lockout, audited sessions).
- 2. Admin CRUD (users, machines, operation templates, projects / assemblies / parts) with content-addressed STEP / PDF / DXF / SVG file uploads.
- 3. Operation authoring with per-operation QR tokens (192-bit, base64url).
- 4. Operator scan flow — phone scan resolves
/op/scan/<token>, single-claim enforced at DB level, Start / Pause / Done with inline QC for steps that require it, TimeLog rows for every claim. - 5. PDF traveler generation — per-operation card + per-part cover sheet with the full operation list and file manifest. Printed via
pdf-lib(no native deps). - 6. Fasteners + purchase orders — per-project BOM of fasteners with unresolved-need rollups, PO lifecycle (
draft → sent → partial → received, orcancelled), per-line receipt entry with auto-advance, and vendor-ready PDF downloads. - 8. In-browser STEP viewer — OpenCascade (WASM, via
occt-import-js) parses STEP/STP,three.jsrenders with OrbitControls. Thumbnails are captured from the first rendered frame, uploaded to the content-addressed file store, and displayed on the assembly parts list. No native deps, no server-side GL.
Planned (not yet shipped): dashboard (step 7) → dedicated QC operations (9) → OpenAPI docs + backups (10).
Core concepts
…(truncated — see repo)
Notes
- Project file auto-created from repo documentation.