open-notebook/docs/5-CONFIGURATION/index.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

8.2 KiB

Configuration - Essential Settings

Configuration is how you customize Open Notebook for your specific setup. This section covers what you need to know.


What Needs Configuration?

Three things:

  1. AI Provider — Which LLM/embedding service you're using (OpenAI, Anthropic, Ollama, etc.)
  2. Database — How to connect to SurrealDB (usually pre-configured)
  3. Server — API URL, ports, timeouts (usually auto-detected)

Quick Decision: Which Provider?

Option 1: Cloud Provider (Fastest)

  • OpenRouter (recommended) (access to all models with one key)
  • OpenAI (GPT)
  • Anthropic (Claude)
  • Google Gemini (multi-modal, long context)
  • Groq (ultra-fast inference)

Setup: Get API key → Add credential in Settings UI → Done

→ Go to AI Providers Guide

Option 2: Local (Free & Private)

  • Ollama (open-source models, on your machine)

→ Go to Ollama Setup

Option 3: OpenAI-Compatible

  • LM Studio (local)
  • Custom endpoints

→ Go to OpenAI-Compatible Guide


Configuration File

Use the right file depending on your setup.

.env (Local Development)

You will only use .env if you are running Open Notebook locally.

Located in: project root
Use for: Development on your machine
Format: KEY=value, one per line

docker.env (Docker Deployment)

You will use this file to hold your environment variables if you are using docker-compose and prefer not to put the variables directly in the compose file.

Located in: project root (or ./docker)
Use for: Docker deployments
Format: Same as .env
Loaded by: docker-compose.yml

Most Important Settings

All of the settings provided below are to be placed inside your environment file (.env or docker.env depending on your setup).

Surreal Database

This is the database used by the app.

SURREAL_URL=ws://surrealdb:8000/rpc
SURREAL_USER=root
SURREAL_PASSWORD=root  # Change in production!
SURREAL_NAMESPACE=open_notebook
SURREAL_DATABASE=open_notebook

The only thing that is critical to not miss is the hostname in the SURREAL_URL. Check what URL to use based on your deployment, here.

AI Provider (Credentials)

We need access to LLMs in order for the app to work. AI provider credentials are configured via the Settings UI:

  1. Set OPEN_NOTEBOOK_ENCRYPTION_KEY in your environment (required for storing credentials)
  2. Start services
  3. Go to Settings → API Keys → Add Credential
  4. Select your provider, paste your API key
  5. Test ConnectionDiscover ModelsRegister Models
# Required in your .env or docker-compose.yml:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key

Ollama users: Add an Ollama credential in Settings → API Keys with the correct base URL. See Ollama Setup for network configuration help.

LM Studio / OpenAI-Compatible: Add an OpenAI-Compatible credential in Settings → API Keys. See OpenAI-Compatible Guide.

API URL (If Behind Reverse Proxy)

You only need to worry about this if you are deploying on a proxy or if you are changing port information. Otherwise, skip this.

API_URL=https://your-domain.com
# Usually auto-detected. Only set if needed.

Auto-detection works for most setups.


Configuration by Scenario

Scenario 1: Docker on Localhost (Default)

# In docker.env:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
# Everything else uses defaults
# Then configure AI provider in Settings → API Keys

Scenario 2: Docker on Remote Server

# In docker.env:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
API_URL=http://your-server-ip:5055

Scenario 3: Behind Reverse Proxy (Nginx/Cloudflare)

# In docker.env:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
API_URL=https://your-domain.com
# The reverse proxy handles HTTPS

Scenario 4: Using Ollama Locally

# In .env:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
# Then add Ollama credential in Settings → API Keys

Scenario 5: Using Azure OpenAI

# In docker.env:
OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
# Then add Azure OpenAI credential in Settings → API Keys

Configuration Sections

AI Providers

  • OpenAI configuration
  • Anthropic configuration
  • Google Gemini configuration
  • Groq configuration
  • Ollama configuration
  • Azure OpenAI configuration
  • OpenAI-compatible configuration

Database

  • SurrealDB setup
  • Connection strings
  • Database vs. namespace
  • Running your own SurrealDB

Advanced

  • Ports and networking
  • Timeouts and concurrency
  • SSL/security
  • Retry configuration
  • Worker concurrency
  • Language models & embeddings
  • Speech-to-text & text-to-speech
  • Debugging and logging

Reverse Proxy

  • Nginx, Caddy, Traefik configs
  • Custom domain setup
  • SSL/HTTPS configuration
  • Coolify and other platforms

Security

  • Password protection
  • API authentication
  • Production hardening
  • Firewall configuration

Local TTS

  • Speaches setup for local text-to-speech
  • GPU acceleration
  • Voice options
  • Docker networking

Local STT

  • Speaches setup for local speech-to-text
  • Whisper model options
  • GPU acceleration
  • Docker networking

Ollama

  • Setting up and pointing to an Ollama server
  • Downloading models
  • Using embedding

OpenAI-Compatible Providers

  • LM Studio, vLLM, Text Generation WebUI
  • Connection configuration
  • Docker networking
  • Troubleshooting

Complete Reference

  • All environment variables
  • Grouped by category
  • What each one does
  • Default values

How to Add Configuration

Method 1: Settings UI (For AI Provider Credentials)

The recommended way to configure AI providers:

1. Open Open Notebook in your browser
2. Go to Settings → API Keys
3. Click "Add Credential"
4. Select provider, enter API key
5. Click Save, then Test Connection
6. Click Discover Models → Register Models

No file editing, no restarts. Credentials stored securely (encrypted) in database.

Full Guide: API Configuration

Method 2: Edit .env File (Infrastructure Settings)

For database, network, and encryption key settings:

1. Open .env in your editor
2. Set OPEN_NOTEBOOK_ENCRYPTION_KEY and database vars
3. Save
4. Restart services

Method 3: Set Docker Environment (Deployment)

# In docker-compose.yml:
services:
  api:
    environment:
      - OPEN_NOTEBOOK_ENCRYPTION_KEY=my-secret-key
      - API_URL=https://your-domain.com

Verification

After configuration, verify it works:

1. Open your notebook
2. Go to Settings → Models
3. You should see your configured provider
4. Try a simple Chat question
5. If it responds, configuration is correct!

Common Mistakes

Mistake Problem Fix
No credential configured Models not available Add credential in Settings → API Keys
Missing encryption key Can't save credentials Set OPEN_NOTEBOOK_ENCRYPTION_KEY
Wrong database URL Can't start API Check SURREAL_URL format
Expose port 5055 "Can't connect to server" Expose 5055 in docker-compose
Typo in env var Settings ignored Check spelling (case-sensitive!)
Don't restart Old config still used Restart services after env changes

What Comes After Configuration

Once configured:

  1. Quick Start — Run your first notebook
  2. Installation — Multi-route deployment guides
  3. User Guide — How to use each feature

Getting Help


Summary

Minimal configuration to run:

  1. Set OPEN_NOTEBOOK_ENCRYPTION_KEY in your environment
  2. Start services
  3. Add AI provider credential in Settings → API Keys
  4. Done!

Everything else is optional optimization.