Commit f3fbc63
fix: use absolute DB paths to prevent seed data loss across restarts
Root cause: MEMORY_DB_PATH and DOJO_CAS_PATH defaulted to relative paths
("dojo_memory.db", "dojo-skills.db"). When the VPS working directory changed
between deploys, the relative path resolved to a new location — silently
creating a fresh empty database while the old one sat orphaned.
Fix: default to ~/.dojo/memory.db and ~/.dojo/skills.db (absolute paths
under the user's home directory). The directory is created automatically
by NewMemoryManager. Environment variables still override for custom paths.
This explains why seeds planted via dojo_seed_create vanished after v3.1.1
deploy — the Gateway restarted from a different CWD and connected to a
different (empty) database file.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>1 parent a9d1e79 commit f3fbc63
1 file changed
Lines changed: 14 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
269 | 269 | | |
270 | 270 | | |
271 | 271 | | |
272 | | - | |
| 272 | + | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
273 | 277 | | |
274 | 278 | | |
275 | 279 | | |
| |||
520 | 524 | | |
521 | 525 | | |
522 | 526 | | |
523 | | - | |
| 527 | + | |
524 | 528 | | |
525 | 529 | | |
526 | 530 | | |
| |||
673 | 677 | | |
674 | 678 | | |
675 | 679 | | |
| 680 | + | |
| 681 | + | |
| 682 | + | |
| 683 | + | |
| 684 | + | |
| 685 | + | |
| 686 | + | |
| 687 | + | |
676 | 688 | | |
677 | 689 | | |
678 | 690 | | |
| |||
0 commit comments