peter
d30e2436ab
Removes the "Daybook" name from everything user- and agent-facing, since no agents are configured yet and this is the cheap moment to do it. - UI brand, docs, README, CLAUDE.md -> AgentFeed. - Ingest env vars DAYBOOK_URL/TOKEN/SOURCE/DATA_DIR/BIND_ADDR/HOST_DATA_DIR/ KEY_PROVISIONING_API -> AGENTFEED_* (token *values* unchanged). - Skill: skills/daybook-posting -> skills/agentfeed-posting, daybook_post.py -> agentfeed_post.py (+ scripts/ wrapper and its test). - static/daybook.css -> static/agentfeed.css; localStorage daybook.* -> agentfeed.*; templatetag daybook_extras -> agentfeed_extras; multipart boundaries; json/csv viewer element ids; daybook_exception_handler -> agentfeed_exception_handler; compose service/container -> agentfeed. - Key-provisioning API now OFF by default (independent of DEBUG); enable with AGENTFEED_KEY_PROVISIONING_API=1 on test installs only. - Posting helper now points at Settings -> API Keys. Deferred on purpose (a later, separate step): the Django package `daybook_project`, the `/opt/daybook` install path, and the Forgejo repo name. The sibling AGENT_DAYBOOK__LLM_TEST name is intentionally untouched. Full suite: 129 passing; live server verified serving under the new name. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
33 lines
1.3 KiB
YAML
33 lines
1.3 KiB
YAML
# ${VAR} substitution below (AGENTFEED_BIND_ADDR, AGENTFEED_HOST_DATA_DIR) reads
|
|
# from deploy/.env because Compose resolves .env relative to *this file's*
|
|
# directory, not the caller's cwd. That relies on being invoked as
|
|
# `docker compose -f deploy/docker-compose.yml` from the repo root, per
|
|
# deploy/cloud_agent_deploy.md and docs/deployment.md. If that invocation
|
|
# pattern ever changes, re-verify these still resolve — a silent fallback to
|
|
# the defaults (0.0.0.0 bind, ./data) would be a security regression, not
|
|
# just a broken build.
|
|
services:
|
|
agentfeed:
|
|
build:
|
|
context: ..
|
|
dockerfile: deploy/Dockerfile
|
|
container_name: agentfeed
|
|
restart: unless-stopped
|
|
env_file:
|
|
- .env
|
|
mem_limit: 384m
|
|
mem_reservation: 128m
|
|
ports:
|
|
- "${AGENTFEED_BIND_ADDR:-0.0.0.0}:8000:8000"
|
|
volumes:
|
|
- ${AGENTFEED_HOST_DATA_DIR:-./data}:/data
|
|
healthcheck:
|
|
# Hit the login page, not /api/capabilities: capabilities returns 403
|
|
# when unauthenticated, and `curl --fail` treats 403 as an error, which
|
|
# would mark a perfectly healthy container unhealthy. The login page
|
|
# serves 200 without auth and still proves Django is up and responding.
|
|
test: ["CMD", "curl", "-fsS", "http://127.0.0.1:8000/accounts/login/"]
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 5
|
|
start_period: 20s
|