config-file.yaml

# Example configuration for reading from a local file
#
# This configuration reads registry data from a local JSON file on the filesystem.
# This is useful for:
#   - Testing and development
#   - Reading from mounted volumes (e.g., ConfigMaps mounted as files)
#   - Pre-downloaded or statically provided registry data
#
# Usage:
#   thv-registry-api serve --config examples/config-file.yaml

# Sources configuration (can have multiple sources)
sources:
  - name: local-file

    # Local file configuration
    file:
      # Path to the registry.json file (absolute or relative)
      # Can be a mounted ConfigMap, downloaded file, or any JSON file
      path: ./data/registry.json

    # Per-registry automatic synchronization policy
    syncPolicy:
      # Sync interval - how often to check if the file has changed
      # For local files, you can use shorter intervals
      interval: "5m"

    # Optional: Per-registry filter configuration to include/exclude specific servers
    # filter:
    #   # Name-based filtering
    #   names:
    #     include:
    #       - "official/*"
    #       - "stacklok/*"
    #     exclude:
    #       - "*/deprecated"
    #
    #   # Tag-based filtering
    #   tags:
    #     include:
    #       - "production"
    #       - "stable"
    #     exclude:
    #       - "experimental"

registries:
  - name: default
    sources: ["local-file"]

auth:
  mode: anonymous

# PostgreSQL database configuration (required)
# Passwords are managed via PostgreSQL's pgpass file (~/.pgpass or $PGPASSFILE)
# See: https://www.postgresql.org/docs/current/libpq-pgpass.html
database:
  host: localhost
  port: 5432
  user: thv_user
  database: toolhive_registry
  # For development, disable SSL (NOT for production!)
  sslMode: disable