-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathwrangler.toml.example
More file actions
45 lines (38 loc) · 1.6 KB
/
Copy pathwrangler.toml.example
File metadata and controls
45 lines (38 loc) · 1.6 KB
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
# Recall — Cloudflare Workers configuration template
#
# Copy this file to `wrangler.toml` and fill in the placeholders.
# The `database_id` is generated when you run `wrangler d1 create`.
# Everything else can stay as-is unless you want to customize names.
#
# Secrets are NOT set here. After deploy, run:
# wrangler secret put MEMORY_API_KEY
name = "recall"
main = "src/index.ts"
compatibility_date = "2025-03-01"
# Deploy to workers.dev by default. Users who want a custom domain
# can override this with routes (see Custom Domain section in the
# README).
workers_dev = true
# Disable preview URLs. The worker is intended to be bound to your
# MCP client by a single stable URL — preview URLs (pr/branch-specific
# deploy previews) would just create churn and potentially leak
# unprotected endpoints. If you need preview URLs for iteration,
# set this to true and run the setup.sh deploy on a non-production env.
preview_urls = false
# ── D1 (SQLite) — stores memory metadata, content, and FTS5 index ──
[[d1_databases]]
binding = "DB"
database_name = "recall"
database_id = "REPLACE_WITH_YOUR_D1_DATABASE_ID"
# ── Vectorize — semantic search index (1024D, cosine, for bge-m3) ──
[[vectorize]]
binding = "VECTORS"
index_name = "recall-vectors"
# ── Workers AI — embeddings (bge-m3) and reranking (bge-reranker-base) ──
[ai]
binding = "AI"
# ── Weekly memory consolidation — runs Sunday 03:00 UTC by default ──
# Generates a read-only report of duplicates + stale memories, stored
# as a searchable memory keyed `_system.consolidation-report`.
[triggers]
crons = ["0 3 * * SUN"]