Skip to main content
Humancheck uses a YAML configuration file (humancheck.yaml) to control its behavior. This guide explains all available configuration options.

Configuration File Location

The configuration file is located at:
  • Default: ./humancheck.yaml (in the current directory)
  • Custom: Specify with --config PATH flag

Creating Configuration

Initialize a new configuration file:
This creates a humancheck.yaml file with default settings.

Configuration Options

API Server Configuration

  • api_host: Host to bind the API server (default: 0.0.0.0)
  • api_port: Port for the API server (default: 8000)

Dashboard Configuration

  • streamlit_host: Host to bind the dashboard (default: 0.0.0.0)
  • streamlit_port: Port for the dashboard (default: 8501)

Database Configuration

SQLite (Development)

  • storage: Database type (sqlite or postgresql)
  • db_path: Path to SQLite database file

PostgreSQL (Production)

  • db_url: PostgreSQL connection URL

Review Configuration

  • confidence_threshold: Minimum confidence score for auto-approval
  • require_review_for: List of task types that always require review

Default Reviewers

  • default_reviewers: List of email addresses for default reviewers (used when no routing rules match)

Logging Configuration

  • log_level: Logging level
  • log_file: Path to log file (set to null to disable file logging)

MCP Configuration

  • mcp_server_name: Name of the MCP server
  • mcp_version: MCP server version

Security Configuration

  • enable_auth: Enable API key authentication
  • api_key: API key for authentication (required if enable_auth: true)

Multi-tenancy Configuration

  • default_organization_name: Name of the default organization

Environment Variables

You can override configuration values using environment variables with the HUMANCHECK_ prefix:

Complete Example

Production Configuration

For production deployments, consider:
  1. Use PostgreSQL: Switch from SQLite to PostgreSQL
  2. Enable Authentication: Set enable_auth: true and provide an API key
  3. Set Logging: Configure log file path
  4. Use Environment Variables: Store sensitive values in environment variables
  5. Configure Backup: Set up database backups

Next Steps