peter/daybook
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Refine AgentFeed UI and local workflow

Browse source
This commit is contained in:
peter 2026-06-11 14:01:16 +01:00
parent 3179f832fc
commit ba9f5eb168
29 changed files with 2986 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

28
_archive_/hosts/README.md Normal file
View file

@ -0,0 +1,28 @@
# Daybook Hosts
This directory tracks Daybook deployment targets for fast iteration.
These notes are intentionally app-specific. They should answer: where is Daybook running, how do we update it, how do we verify it, and where does persistent Daybook data live?
They are not a replacement for host administration docs. For the Proxmox NUC, the canonical infrastructure source remains the NUC ops repo:
```text
C:\Users\ritte\_PR_DEV_\LIVE_ADMIN\NUC_SERVER
```
## Deployment Targets
| Host | Status | Notes |
|---|---|---|
| [NUC Daybook](nuc-daybook.md) | Live | Current local/LAN deployment in Proxmox LXC `128` |
| [Cloud template](cloud-template.md) | Planned | Fill this in when a hosted/cloud instance is created |
## Documentation Rule
When a Daybook deployment changes, update the matching file here and the broader handoff doc if takeover facts changed:
```text
planning/daybook-container-handoff.md
```
When the NUC host/container configuration changes, also update the NUC ops knowledge base.