chrysopedia/CLAUDE.md
jlightner 17b43d9778 feat: Added LightRAG /query/data as primary search engine with file_sou…
- "backend/config.py"
- "backend/search_service.py"

GSD-Task: S01/T01
2026-04-04 04:44:24 +00:00

48 lines
1.5 KiB
Markdown

# Chrysopedia — Development Reference
## ⚠️ Canonical Development Directory
**This is NOT the canonical development directory.**
The production codebase and all future development happens on **ub01**:
```
ssh ub01
cd /vmPool/r/repos/xpltdco/chrysopedia
```
**Git:** https://git.xpltd.co/xpltdco/chrysopedia (Forgejo, xpltdco org)
## Why?
The Docker Compose stack runs on ub01 with bind mounts at `/vmPool/r/services/chrysopedia_*`. Development, deployment, and testing all happen from the ub01 clone. This directory (`/home/aux/projects/content-to-kb-automator`) was the initial workspace used during M001 development and should not be used for future work.
## Stack Info
- **Web UI:** http://ub01:8096
- **API Health:** http://ub01:8096/health
- **PostgreSQL:** ub01:5433 (user: chrysopedia)
- **Compose project:** xpltd_chrysopedia
- **Compose path:** /vmPool/r/compose/xpltd_chrysopedia/docker-compose.yml (symlink to repo)
- **Services:** chrysopedia-db, chrysopedia-redis, chrysopedia-qdrant, chrysopedia-ollama, chrysopedia-api, chrysopedia-worker, chrysopedia-web-8096
## Quick Commands (on ub01)
```bash
# Check status
docker ps --filter name=chrysopedia
# Rebuild and restart after code changes
cd /vmPool/r/repos/xpltdco/chrysopedia
git pull
docker compose build && docker compose up -d
# Run Alembic migrations
docker exec chrysopedia-api alembic upgrade head
# View worker logs
docker logs -f chrysopedia-worker
# View API logs
docker logs -f chrysopedia-api
```