tblumer/obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix architecture diagram issues

Browse Source 
- Changed Core Backend to 'Go (REST API)' (removed gRPC, kept REST)
- Removed BLE from IoT (not supported yet)
- Fixed text overflow in boxes by adjusting layout and labels
- Updated description to reflect REST-only API
This commit is contained in:
TNB
2026-07-07 09:36:26 -04:00
parent d329f89c0f
commit fceef6f42b
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TallyFlow/TallyFlow-Architecture.md
+2 -2
View File
@@ -7,7 +7,7 @@
TallyFlow is built around exactly **five primary components**, with **Core** as the central hub that owns the database.
### 1. Core (Central)
- **Core Backend** (Go) positioned in the center
- **Core Backend** (Go) positioned in the center — provides the REST API
- **Core Web UI** (Vue.js) on the left — consumes the Core API
- Owns MongoDB (assets, tags, photos, zones, events)
- Single API integration point for all other components
@@ -45,4 +45,4 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
- **Print** additionally supports asset registration back into Core
- Core Web UI communicates with Core Backend via the same API used by other components
This structure was verified by reviewing the actual source repositories in `~/src/`. All external modules interact exclusively through Core’s API layer.
This structure was verified by reviewing the actual source repositories in `~/src/`. All external modules interact exclusively through Core’s REST API layer.