vault backup: 2026-05-06 13:30:02
This commit is contained in:
parent
bc402e3c27
commit
ba4eef0817
2 changed files with 4 additions and 0 deletions
|
|
@ -104,6 +104,7 @@ cd frontend && npm run dev
|
|||
## Change Log
|
||||
| Date | Requested | Changed | Files |
|
||||
|------|-----------|---------|-------|
|
||||
| 2026-05-06 | Report automation | Per-user CSV generation from JSON files, git-based deployment with deploy keys and update.sh script | baic_messages.json, baic_conversations.json, update.sh, .env |
|
||||
| 2026-05-06 | Per-User Report feature | New Per-User Report tab, bar chart, user message table, export button | index.html, assets/ |
|
||||
| 2026-05-06 | Per-User Report | index.html, assets/, git push (46ccccc) | index.html, assets/ |
|
||||
| 2026-05-06 | Per-user report feature | Frontend components updated, dist files deployed | frontend/src/*, dist/index.html |
|
||||
|
|
|
|||
|
|
@ -101,3 +101,6 @@ tags: [daily]
|
|||
- 13:27 | `baic_dashboard`
|
||||
- **Asked:** Implement a per-user report feature for BAIC UK dashboard with monthly data exports.
|
||||
- **Done:** Added Per-User Report tab to BAIC dashboard with bar chart, user message counts table, and export functionality.
|
||||
- 13:28 | `baic_dashboard`
|
||||
- **Asked:** How should we implement a monthly per-user report system for BAIC UK and set up deployment?
|
||||
- **Done:** Proposed a git-based deployment strategy using SSH deploy keys and an update script for safe server deployments.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue