Improve CV parsing and profile editor flow
This commit is contained in:
@@ -25,7 +25,7 @@ Job Tracker is a simple, self-hosted app for tracking job applications with a Re
|
||||
|
||||
## Quickstart (Docker)
|
||||
|
||||
This runs: frontend (nginx), backend API, and the AI service.
|
||||
This runs: frontend (nginx), backend API, the local AI service, and an Ollama container for hybrid CV block classification.
|
||||
|
||||
1) Create a `.env` file next to `docker-compose.yml` (you can start from `.env.example`).
|
||||
|
||||
@@ -108,9 +108,15 @@ The API calls a local FastAPI service to generate summaries. If it’s not runni
|
||||
With Docker (recommended):
|
||||
|
||||
```bash
|
||||
docker compose up --build ai-service
|
||||
# One command for local Ollama startup + pull + AI-service restart
|
||||
OLLAMA_MODEL=qwen2.5:7b ./scripts/start-ollama-cv.sh
|
||||
|
||||
# Then start the rest of the app if needed
|
||||
docker compose up --build -d backend frontend
|
||||
```
|
||||
|
||||
The first Ollama startup is usually quick, but the first model pull and first generation can take a while. After the model is cached in the `ollama_data` volume, later restarts are much faster.
|
||||
|
||||
Or run directly from `tools/summarizer/` (see `tools/summarizer/README.md`).
|
||||
|
||||
## Configuration
|
||||
|
||||
Reference in New Issue
Block a user