AltimateAI / AltimateAI/altimate-code

serve: persist session traces across container restarts (Dockerfile VOLUME / XDG guidance)

未關閉
#915 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
TypeScript
星號
811
分支
134
平均合併
3 天 2 小時
30 天內合併 PR
50

描述

Found during the v0.8.6 release review (Chaos/k8s persona). Deferred because it's a deployment/Dockerfile behavior change that needs design thought, not a quick fix.

Now that `altimate serve` writes session traces (#886), traces land under `$XDG_DATA_HOME/altimate-code/traces/` (default `~/.local/share/altimate-code/traces/`). In a container this is the ephemeral filesystem — a pod restart / rolling update / OOMKill silently drops the entire trace history.

Proposed:
- Document a recommended volume mount for the trace dir in the deploy/Docker docs.
- Consider `VOLUME`/`ENV XDG_DATA_HOME` in `packages/opencode/Dockerfile` (carefully — it changes default paths).
- Reference `tracing.dir` config as the override knob.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。