open-notebook/docs/7-DEVELOPMENT/development-setup.md
Luis Novo 3f352cfcce
feat: credential-based API key management (#477) (#540)
* feat: replace provider config with credential-based system (#477)

Introduce a new credential management system replacing the old
ProviderConfig singleton and standalone Models page. Each credential
stores encrypted API keys and provider-specific configuration with
full CRUD support via a unified settings UI.

Backend:
- Add Credential domain model with encrypted API key storage
- Add credentials API router (CRUD, discovery, registration, testing)
- Add encryption utilities for secure key storage
- Add key_provider for DB-first env-var fallback provisioning
- Add connection tester and model discovery services
- Integrate ModelManager with credential-based config
- Add provider name normalization for Esperanto compatibility
- Add database migrations 11-12 for credential schema

Frontend:
- Rewrite settings/api-keys page with credential management UI
- Add model discovery dialog with search and custom model support
- Add compact default model assignments (primary/advanced layout)
- Add inline model testing and credential connection testing
- Add env-var migration banner
- Update navigation to unified settings page
- Remove standalone models page and old settings components

i18n:
- Update all 7 locale files with credential and model management keys

Closes #477

Co-Authored-By: JFMD <git@jfmd.us>
Co-Authored-By: OraCatQAQ <570768706@qq.com>

* fix: address PR #540 review comments

- Fix docs referencing removed Models page
- Fix error-handler returning raw messages instead of i18n keys
- Fix auth.py misleading docstring and missing no-password guard
- Fix connection_tester using wrong env var for openai_compatible
- Add provision_provider_keys before model discovery/sync
- Update CLAUDE.md to reflect credential-based system
- Fix missing closing brace in api-keys page useEffect

* fix: add logging to credential migration and surface errors in UI

- Add comprehensive logging to migrate-from-env and
  migrate-from-provider-config endpoints (start, per-provider
  progress, success/failure with stack traces, final summary)
- Fix frontend migration hooks ignoring errors array from response
- Show error toast when migration fails instead of "nothing to migrate"
- Invalidate status/envStatus queries after migration so banner updates

* docs: update CLAUDE.md files for credential system

Replace stale ProviderConfig and /api-keys/ references across 8 CLAUDE.md
files to reflect the new Credential-based system from PR #540.

* docs: update user documentation for credential-based system

Replace env var API key instructions with Settings UI credential
workflow across all user-facing documentation. The new flow is:
set OPEN_NOTEBOOK_ENCRYPTION_KEY → start services → add credential
in Settings UI → test → discover models → register.

- Rewrite ai-providers.md, api-configuration.md, environment-reference.md
- Update all quick-start guides and installation docs
- Update ollama.md, openai-compatible.md, local-tts/stt networking sections
- Update reverse-proxy.md, development-setup.md, security.md
- Fix broken links to non-existent docs/deployment/ paths
- Add credentials endpoints to api-reference.md
- Move all API key env vars to deprecated/legacy sections

* chore: bump version to 1.7.0-rc1

Release candidate for credential-based provider management system.

* fix: initialize provider before try block in test_credential

Prevents UnboundLocalError when Credential.get() throws (e.g.,
invalid credential_id) before provider is assigned.

* fix: reorder down migration to drop index before table

Removes duplicate REMOVE FIELD statement and reorders so the index
is dropped before the table, preventing rollback failures.

* refactor: simplify encryption key to always derive via SHA-256

Remove the dual code path in _ensure_fernet_key() that detected native
Fernet keys. Since the credential system is new, always deriving via
SHA-256 removes unnecessary complexity. Also removes the generate_key()
function and Fernet.generate_key() references from docs.

* fix: correct mock patch targets in embedding tests and URL validation

Fix embedding tests patching wrong module path for model_manager
(was targeting open_notebook.utils.embedding.model_manager but it's
imported locally from open_notebook.ai.models). Also fix URL validation
to allow unresolvable hostnames since they may be valid in the
deployment environment (e.g., Azure endpoints, internal DNS).

* feat: add global setup banner for encryption and migration status

Show a persistent banner in AppShell when encryption key is missing
(red) or env var API keys can be migrated (amber), so users see
these prompts on every page instead of only on Settings > API Keys.

Includes a docs link for the encryption banner and i18n support
across all 7 locales.

* docs: several improvements to docker-compose e env examples

* Update README.md

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* docs: fix env var format in README and update model setup instructions

Align the encryption key snippet in README Step 2 with the list
format used in the compose file. Replace deprecated "Settings →
Models" instructions with credential-based Discover Models flow.

* fix: address credential system review issues

- Fix SSRF bypass via IPv4-mapped IPv6 addresses (::ffff:169.254.x.x)
- Fix TTS connection test missing config parameter
- Add Azure-specific model discovery using api-key auth header
- Add Vertex static model list for credential-based discovery
- Fix PROVIDER_DISCOVERY_FUNCTIONS incorrect azure/vertex mapping
- Extract business logic to api/credentials_service.py (service layer)
- Move credential Pydantic schemas to api/models.py
- Update tests to use new service imports and ValueError assertions

* fix: sanitize error responses and migrate key_provider to Credential

- Replace raw exception messages in all credential router 500 responses
  with generic error strings (internal details logged server-side only)
- Refactor key_provider.py to use Credential.get_by_provider() instead
  of deprecated ProviderConfig.get_instance()
- Remove unused functions (get_provider_configs, get_default_api_key,
  get_provider_config) that were dead code

---------

Co-authored-by: JFMD <git@jfmd.us>
Co-authored-by: OraCatQAQ <570768706@qq.com>
2026-02-10 08:30:22 -03:00

9.1 KiB

Local Development Setup

This guide walks you through setting up Open Notebook for local development. Follow these steps to get the full stack running on your machine.

Prerequisites

Before you start, ensure you have the following installed:

  • Python 3.11+ - Check with: python --version
  • uv (recommended) or pip - Install from: https://github.com/astral-sh/uv
  • SurrealDB - Via Docker or binary (see below)
  • Docker (optional) - For containerized database
  • Node.js 18+ (optional) - For frontend development
  • Git - For version control

Step 1: Clone and Initial Setup

# Clone the repository
git clone https://github.com/lfnovo/open-notebook.git
cd open-notebook

# Add upstream remote for keeping your fork updated
git remote add upstream https://github.com/lfnovo/open-notebook.git

Step 2: Install Python Dependencies

# Using uv (recommended)
uv sync

# Or using pip
pip install -e .

Step 3: Environment Variables

Create a .env file in the project root with your configuration:

# Copy from example
cp .env.example .env

Edit .env with your settings:

# Database
SURREAL_URL=ws://localhost:8000/rpc
SURREAL_USER=root
SURREAL_PASSWORD=password
SURREAL_NAMESPACE=open_notebook
SURREAL_DATABASE=development

# Credential encryption (required for storing API keys)
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-dev-secret-key

# Application
APP_PASSWORD=  # Optional password protection
DEBUG=true
LOG_LEVEL=DEBUG

AI Provider Configuration

After starting the API and frontend, configure your AI provider via the Settings UI:

  1. Open http://localhost:3000SettingsAPI Keys
  2. Click Add Credential → Select your provider
  3. Enter your API key (get from provider dashboard)
  4. Click Save, then Test Connection
  5. Click Discover ModelsRegister Models

Popular providers:

For local development, you can also use:

  • Ollama - Run locally without API keys (see "Local Ollama" below)

Note: API key environment variables (e.g., OPENAI_API_KEY) are deprecated. Use the Settings UI to manage credentials instead.

Step 4: Start SurrealDB

# Start SurrealDB in memory
docker run -d --name surrealdb -p 8000:8000 \
  surrealdb/surrealdb:v2 start \
  --user root --pass password \
  --bind 0.0.0.0:8000 memory

# Or with persistent storage
docker run -d --name surrealdb -p 8000:8000 \
  -v surrealdb_data:/data \
  surrealdb/surrealdb:v2 start \
  --user root --pass password \
  --bind 0.0.0.0:8000 file:/data/surreal.db

Option B: Using Make

make database

Option C: Using Docker Compose

docker compose up -d surrealdb

Verify SurrealDB is Running

# Should show server information
curl http://localhost:8000/

Step 5: Run Database Migrations

Database migrations run automatically when you start the API. The first startup will apply any pending migrations.

To verify migrations manually:

# API will run migrations on startup
uv run python -m api.main

Check the logs - you should see messages like:

Running migration 001_initial_schema
Running migration 002_add_vectors
...
Migrations completed successfully

Step 6: Start the API Server

In a new terminal window:

# Terminal 2: Start API (port 5055)
uv run --env-file .env uvicorn api.main:app --host 0.0.0.0 --port 5055

# Or using the shortcut
make api

You should see:

INFO:     Application startup complete
INFO:     Uvicorn running on http://0.0.0.0:5055

Verify API is Running

# Check health endpoint
curl http://localhost:5055/health

# View API documentation
open http://localhost:5055/docs

Step 7: Start the Frontend (Optional)

If you want to work on the frontend, start Next.js in another terminal:

# Terminal 3: Start Next.js frontend (port 3000)
cd frontend
npm install  # First time only
npm run dev

You should see:

> next dev
  ▲ Next.js 16.x
  - Local:        http://localhost:3000

Access the Frontend

Open your browser to: http://localhost:3000

Verification Checklist

After setup, verify everything is working:

  • SurrealDB: curl http://localhost:8000/ returns content
  • API: curl http://localhost:5055/health returns {"status": "ok"}
  • API Docs: open http://localhost:5055/docs works
  • Database: API logs show migrations completing
  • Frontend (optional): http://localhost:3000 loads

Starting Services Together

Quick Start All Services

make start-all

This starts SurrealDB, API, and frontend in one command.

Terminal 1 - Database:

make database

Terminal 2 - API:

make api

Terminal 3 - Frontend:

cd frontend && npm run dev

Development Tools Setup

Install git hooks to automatically check code quality:

uv run pre-commit install

Now your commits will be checked before they're made.

Code Quality Commands

# Lint Python code (auto-fix)
make ruff
# or: ruff check . --fix

# Type check Python code
make lint
# or: uv run python -m mypy .

# Run tests
uv run pytest

# Run tests with coverage
uv run pytest --cov=open_notebook

Common Development Tasks

Running Tests

# Run all tests
uv run pytest

# Run specific test file
uv run pytest tests/test_notebooks.py

# Run with coverage report
uv run pytest --cov=open_notebook --cov-report=html

Creating a Feature Branch

# Create and switch to new branch
git checkout -b feature/my-feature

# Make changes, then commit
git add .
git commit -m "feat: add my feature"

# Push to your fork
git push origin feature/my-feature

Updating from Upstream

# Fetch latest changes
git fetch upstream

# Rebase your branch
git rebase upstream/main

# Push updated branch
git push origin feature/my-feature -f

Troubleshooting

"Connection refused" on SurrealDB

Problem: API can't connect to SurrealDB

Solutions:

  1. Check if SurrealDB is running: docker ps | grep surrealdb
  2. Verify URL in .env: Should be ws://localhost:8000/rpc
  3. Restart SurrealDB: docker stop surrealdb && docker rm surrealdb
  4. Then restart with: docker run -d --name surrealdb -p 8000:8000 surrealdb/surrealdb:v2 start --user root --pass password --bind 0.0.0.0:8000 memory

"Address already in use"

Problem: Port 5055 or 3000 is already in use

Solutions:

# Find process using port
lsof -i :5055  # Check port 5055

# Kill process (macOS/Linux)
kill -9 <PID>

# Or use different port
uvicorn api.main:app --port 5056

Module not found errors

Problem: Import errors when running API

Solutions:

# Reinstall dependencies
uv sync

# Or with pip
pip install -e .

Database migration failures

Problem: API fails to start with migration errors

Solutions:

  1. Check SurrealDB is running: curl http://localhost:8000/
  2. Check credentials in .env match your SurrealDB setup
  3. Check logs for specific migration error: make api 2>&1 | grep -i migration
  4. Verify database exists: Check SurrealDB console at http://localhost:8000/

Migrations not applying

Problem: Database schema seems outdated

Solutions:

  1. Restart API - migrations run on startup: make api
  2. Check logs show "Migrations completed successfully"
  3. Verify /migrations/ folder exists and has files
  4. Check SurrealDB is writable and not in read-only mode

Optional: Local Ollama Setup

For testing with local AI models:

# Install Ollama from https://ollama.ai

# Pull a model (e.g., Mistral 7B)
ollama pull mistral

Then configure via the Settings UI:

  1. Go to SettingsAPI KeysAdd CredentialOllama
  2. Enter base URL: http://localhost:11434
  3. Click Save, then Test Connection
  4. Click Discover ModelsRegister Models

Optional: Docker Development Environment

Run entire stack in Docker:

# Start all services
docker compose --profile multi up

# Logs
docker compose logs -f

# Stop services
docker compose down

Next Steps

After setup is complete:

  1. Read the Contributing Guide - contributing.md
  2. Explore the Architecture - Check the documentation
  3. Find an Issue - Look for "good first issue" on GitHub
  4. Set Up Pre-commit - Install git hooks for code quality
  5. Join Discord - https://discord.gg/37XJPXfz2w

Getting Help

If you get stuck:


Ready to contribute? Go to contributing.md for the contribution workflow.