How aues6uen11z/dacapo works
Project Type & Purpose
• DaCapo is a full-stack, desktop GUI application built with Wails (Go backend + Quasar/Vue frontend).
• Purpose: Provide a config-driven graphical script/task manager that pulls remote repos, manages Python venvs, schedules tasks, and presents logs in real time.
File Structure
• Top-level directories:
• frontend/ → Quasar/Vue SPA
• backend/ → Go server with MVC-style controllers
• build/ → Packaging for Windows/macOS (via Wails)
• repos/ → User-managed script repositories
• Backend layers:
• router/ → API routes
• controller/ → Instance, Scheduler, Template, Updater controllers
• model/ → DB definitions, Request/Response structs
• utils/ → Git operations, Logger, WebSocket manager
• Frontend:
• src/pages/ → Views (Home, Instance, Settings, etc.)
• src/components/ → Reusable Vue components
• src/services/ → API wrappers (axios), request/response typings
• wailsjs/ → Auto-generated RPC bindings
Key README Insights
• Configs are JSON/YAML → drives UI generation.
• Features: multi-language, auto-update, scheduler, Python venv management.
• Uses Wails to bundle frontend+backend into a desktop client.
Main Components & Relationships
a. UI Layer (Frontend SPA)
• Quasar/Vue pages & components
• Communicates via Wails RPC or HTTP API over an embedded WebView2/WebKit
b. API/Router (Go)
• router/router.go defines endpoints → mapped to controllers
c. Controllers
• instance_ctrl → CRUD on task instances
• scheduler_ctrl → schedule/trigger tasks
• template_ctrl → load/generate UI from config templates
• updater_ctrl → self-update mechanism
d. Model Layer & Storage
• model/db.go → local database (e.g., SQLite)
• Structs for instance info, template info, scheduler, requests, responses
e. Utilities & Services
• Git utils → clone/pull repos
• Python venv & dependency manager (invoked by controller)
• WS manager → pushes real-time log events back to UI
f. External Dependencies
• Remote Git repositories
• Python interpreter & packages
• File system (for config files, logs, repos)
Architectural Patterns & Design Principles
• MVC-like separation in backend (Router → Controller → Model)
• Event-driven real-time updates via WebSocket
• Plugin/config-driven UI generation (templates in repos/)
• Single-Page Application on frontend with service layer for type safety