- "backend/models.py" - "backend/config.py" - "backend/schemas.py" - "backend/routers/pipeline.py" - "alembic/versions/006_debug_columns.py" GSD-Task: S01/T01
2.1 KiB
2.1 KiB
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
GitHub: https://github.com/xpltdco/chrysopedia (private, 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)
# 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
Remote Host: hal0022 (Whisper Transcription)
- Host alias:
hal0022 - IP: 10.0.0.131
- OS: Windows (domain-joined to a.xpltd.co)
- SSH user:
a\jlightner - SSH key:
~/.ssh/hal0022_ed25519 - Role: GPU workstation for Whisper transcription of video content
Connecting
ssh hal0022
SSH config is already set up in ~/.ssh/config on dev01.
Content Location on hal0022
Video source files reside at:
A:\Education\Artist Streams & Content
Note: This is a Windows path. When accessing via SSH, use the appropriate path format for the shell available on hal0022.