toolhive-registry-server/examples/config-docker-dual.yaml at main · stacklok/toolhive-registry-server · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
# Dual-source configuration for Docker Compose
#
# This configuration demonstrates merging data from two sources backed by the
# same MCP Registry v0.1 file but with different per-source filters. The API
# server combines the filtered subsets and serves them through the unified
# MCP Registry API.
#
# Usage:
#   CONFIG_FILE=config-docker-dual.yaml docker-compose up
#
# This example shows:
# - Two file sources with different sync intervals
# - Per-source filters carving the catalog into a database subset and a
#   version-control subset
# - How the server merges filtered data from multiple sources

# Two file-based sources
sources:
  # Source 1: Database-related servers
  - name: database-servers
    file:
      path: /examples/upstream-registry.json  # All examples files are mounted
    syncPolicy:
      interval: "30s"  # Quick sync for testing
    filter:
      names:
        include:
          - "*/*-mysql-*"
          - "*/genai-*"

  # Source 2: Version-control servers
  - name: version-control-servers
    file:
      path: /examples/upstream-registry.json  # All examples files are mounted
    syncPolicy:
      interval: "45s"  # Different interval
    filter:
      names:
        include:
          - "*/git*"

registries:
  - name: default
    sources: ["database-servers", "version-control-servers"]

# Authentication configuration
auth:
  mode: anonymous

# PostgreSQL database configuration
database:
  host: postgres
  port: 5432
  user: db_app
  migrationUser: db_migrator
  database: registry
  sslMode: disable
  maxOpenConns: 10
  maxIdleConns: 2
  connMaxLifetime: "30m"