Personal job aggregation and tracking app. Fetches jobs from LinkedIn and Jobindex, scores them with a local LLM, and tracks applications via a kanban board.

• Docker + Docker Compose v2
• A local LLM server — see LLM Providers below

For local development only:

• Bun ≥ 1.1

From the terminal in the root directory of the repo:

# 1. Start
docker compose up -d

App is at http://localhost:3000.

./scripts/deploy.sh

Pulls latest master, rebuilds the image, and restarts the container. Data is untouched.

Create a .env file in the project root (see .env.example):

# Authentication — set this to enable password protection
# If not set, the app is accessible without a password (fine for local-only use)
AUTH_SECRET=choose_a_strong_password

# Optional: override default paths
# DB_PATH=./db/jobs.db
# BACKUP_DIR=./backups
# OLLAMA_BASE_URL=http://localhost:11434

The app supports three local LLM providers. Configure the provider, base URL, and model from Settings → LLM Provider — no server restart needed after saving.

# Install (Linux/macOS)
curl -fsSL https://ollama.com/install.sh | sh

# Pull the model and start serving
ollama pull gemma4:26b
ollama serve

1. Download from lmstudio.ai and install
2. In the Discover tab, search for google/gemma-3-27b-it and download it
3. Load the model, open the Local Server tab, and click Start Server (default port 1234)

# Adjust -ngl (GPU layers) and --ctx-size to fit your VRAM
llama-server \
  --model /path/to/gemma-4-26B-A4B-it.gguf \
  --port 8080 \
  --ctx-size 8192 \
  -ngl 99

llama.cpp uses a Gemma chat template and grammar-based JSON sampling automatically.

LLAMACPP_BASE_URL is still honoured as the fallback base URL when using the llama.cpp provider and no URL is saved in Settings. Docker Compose sets it to http://host.docker.internal:8080 automatically.

Set AUTH_SECRET in .env to enable password protection. A login screen appears on first load and sessions last 30 days (in-memory — server restart requires re-login).

Without AUTH_SECRET, the app is unprotected. Fine for local/VPN use, but do not expose it to the internet without setting a password.

1. Open http://localhost:3000
2. Go to Settings
3. Fill in your Preferences — location, tech stack, salary floor, and search terms for each source
4. Add your Resume — paste it as markdown, or use "Ingest resume" to have the AI parse raw text from a PDF/Word copy-paste
5. Click Fetch now in the navbar to pull the first batch of jobs

Runtime data lives on the host and is bind-mounted into the container — it survives image rebuilds and container restarts:

Automatic backups run every 6 hours to backups/ (last 10 kept). Trigger a manual backup or download/delete individual backups from Settings → Database Backups.

To reset the database:

docker compose down
rm db/jobs.db db/jobs.db-wal db/jobs.db-shm 2>/dev/null; true
docker compose up -d

Warning: this deletes all jobs, applications, settings, resume, and preferences.

# Start
docker compose up -d

# Stop
docker compose down

# View logs
docker compose logs -f

# Deploy latest master
./scripts/deploy.sh

# Rebuild without pulling (local changes)
docker compose up -d --build

# Install dependencies
bun install

# Start dev server (server + Vite hot-reload)
bun run dev

• Frontend (Vite): http://localhost:5173
• API server: http://localhost:3000

src/server/       Hono API, scheduler, scrapers, llama.cpp client
src/client/       React frontend (Vite)
db/               SQLite database (gitignored)
backups/          Automatic database backups (gitignored)
data/             resume.md + preferences.md (gitignored)
scripts/          deploy.sh
e2e/              Playwright end-to-end tests

# Server unit + integration tests (uses in-memory DB)
bun run test

# Client component tests
cd src/client && bun run test

# End-to-end tests (requires dev server running)
bun run dev         # in one terminal
bun run test:e2e    # in another

Search terms are configured per-source in Settings → Preferences. The LLM scores each job 0–100 based on your resume and preferences. **The location preference is currently not applied. This repo only searches Alava, Basque Country, Spain.

Server logs are persisted to the database and viewable at /logs. Filter by level, search by text, export to a file, or archive-and-clear from there.