How pinokiofactory/frame-pack works
Project type and purpose
• FramePack is not a full-stack web app but a Pinokio “plugin” or “script package” whose job is to orchestrate the installation, linking, resetting, starting, updating, and Torch-related commands for the upstream FramePack project.
File structure
• Top level:
• pinokio_meta.json – plugin metadata (name, commands exposed to Pinokio)
• pinokio.js – plugin entry point; reads the metadata and hooks the JS scripts into the Pinokio runtime
• install.js, link.js, reset.js, start.js, update.js, torch.js – each implements one Pinokio command
• No nested folders; this is a single-module plugin.
• No database or frontend. It’s purely a CLI-to-external-repo orchestrator.
README
• Confirms this is purely a Pinokio plugin.
• No extra architecture hints beyond pointing to FramePack’s GitHub.
Final advice
• Data/process flow clearly: user input triggers a chain through core → plugin → external.
[User CLI]
↓
[Pinokio Core]
↓
[Plugin Loader]
└─> pinokio_meta.json & pinokio.js
↓
[Command Modules]
├─ install.js → GitHub (FramePack) / npm
├─ link.js → local FS link operations
├─ reset.js → GitHub reset, FS cleanup
├─ start.js → GitHub pull, init & run FramePack
├─ update.js → GitHub pull, npm update
└─ torch.js → Python/Torch environment
↑ ↓
└────────── Console Output ──┘