f915866f83
Expand 03-database.md with complete table structure reference for all 23 tables in the final schema: active QuoteForge tables, competitor subsystem, legacy RFQ tables, and server-side-only tables. Also clarifies access patterns per group and notes removal of qt_client_local_migrations from the schema. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
QuoteForge
Local-first desktop web app for server configuration, quotation, and project work.
Runtime model:
- user work is stored in local SQLite;
- MariaDB is used only for setup checks and background sync;
- HTTP server binds to loopback only.
What the app does
- configuration editor with price refresh from synced pricelists;
- projects with variants and ordered configurations;
- vendor BOM import and PN -> LOT resolution;
- revision history with rollback;
- rotating local backups.
Run
go run ./cmd/qfs
Useful commands:
go run ./cmd/qfs -migrate
go test ./...
go vet ./...
make build-release
On first run the app creates a minimal config.yaml, starts on http://127.0.0.1:8080, and opens /setup if DB credentials were not saved yet.
Documentation
- Shared engineering rules: bible/README.md
- Project architecture: bible-local/README.md
- Release notes:
releases/<version>/RELEASE_NOTES.md
bible-local/ is the source of truth for QuoteForge-specific architecture. If code changes behavior, update the matching file there in the same commit.
Repository map
cmd/ entry points and migration tools
internal/ application code
web/ templates and static assets
bible/ shared engineering rules
bible-local/ project architecture and contracts
releases/ packaged release artifacts and release notes
config.example.yaml runtime config reference