Commit History
-
Update Dockerfile
Verified signature8024333 -
Update scripts/entrypoint.sh
Verified signature4a40ec0
-
Update Dockerfile
Verified signaturec003935 -
Update Dockerfile
Verified signature5b265f4 -
Update Dockerfile
Verified signature5337caa -
Update Dockerfile
Verified signature9397b9b -
Update Dockerfile
Verified signaturee98a7ed -
Update Dockerfile
Verified signature7a4c454 -
Update Dockerfile
Verified signature61b88c3 -
Update Dockerfile
Verified signature24a34ea -
Update Dockerfile
Verified signature3e824d1 -
Update Dockerfile
Verified signaturefc36dc3 -
Update Dockerfile
Verified signature12f3814 -
Update scripts/entrypoint.sh
Verified signature19dc568 -
Update Dockerfile
Verified signatured5f54b5 -
Update Dockerfile
Verified signaturec0e594a -
Update scripts/entrypoint.sh
Verified signature4cdd0be -
Update Dockerfile
Verified signature296497d
-
fix: backup guard — refuse empty dumps, increase history retention
Verified signaturedaf0f64 -
fix: robust process kill and backup guard to prevent death spiral
Verified signature04263be
-
feat: add SKIP_RESTORE env var to break restore-crash death spiral
b8236dd -
fix: protect restore.py exit code from set -e
set -e kills the script on any non-zero return. restore.py returns 2 for 'no backup' which triggered immediate script death. Use 'cmd || var=\0' pattern to safely capture exit codes under set -e.c1ce02e -
fix: restart Hindsight after pg_restore to reload data
pg_restore modifies PG underneath but the running API has cached state. Restarting forces reconnection to the restored database. restore.py now returns exit codes: 0 = data restored (restart needed) 2 = no backup found (skip restart) 1 = errorcded1f5 -
feat: add pg_dump backup/restore for persistent storage
7a352c6 -
Deploy Hindsight API with Groq + local embeddings
Verified signature2d9d1c3 -
initial commit
Verified signature0eac0f0