Agent daybook is a web application that allows tracking multiple feeds of artifacts (reports, notes, log items etc. etc.) - all the things that AI agents would be producing all day long.
peter
f7dd98f6e5
A follow-up review of the previous fix caught that M1's DAYBOOK_HOST_DATA_DIR override wasn't carried through to the backup step or checklist - both still hardcoded deploy/data. Exactly when the override matters (a host with a separate/larger volume), the backup would silently tar the wrong directory while the checklist still read as complete. Backup and checklist now derive the path from deploy/.env instead of restating it. Also documents in docker-compose.yml why the .env interpolation only resolves correctly when invoked as `docker compose -f deploy/docker-compose.yml`, per a non-blocking note from the same review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/commands | ||
| artifacts | ||
| daybook_project | ||
| deploy | ||
| docs | ||
| scripts | ||
| skills/daybook-posting | ||
| static | ||
| templates/artifacts | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| CLAUDE.md | ||
| manage.py | ||
| requirements.txt | ||