Deploy GitChain Edge API

Deploy GitChain Edge API

Deploy a lightweight GitChain search endpoint as a Cloudflare Worker — global, fast, no SSH required.

Process

1. Parse $ARGUMENTS for configuration (namespace filter, custom domain, etc.)
2. Use Cloudflare MCP to:
   • Create/update a Worker named gitchain-search
   • Bind KV namespace for product cache
   • Bind R2 bucket for media assets
   • Set environment variables (GITCHAIN_API_URL, allowed namespaces)
   • Deploy to production
3. Use GitChain status to verify backend connectivity

Worker Architecture

User Request → Cloudflare Edge (300+ cities)
  → KV Cache hit? → Return cached result (<5ms)
  → KV Miss? → Proxy to GitChain API on REACTOR
    → Cache result in KV (TTL: 1h)
    → Return to user (<100ms)

Worker Code Template

The Worker should implement:

• GET /search?q={query}&ns={namespace} — Proxied search with KV cache
• GET /product/{id} — Single container with smart caching
• GET /status — Health check + cache stats
• GET /catalog/{namespace} — Namespace overview (cached 24h)
• CORS headers for browser access
• Rate limiting (100 req/min per IP)

Output Format

# GitChain Edge API Deployed ⚡
**Worker:** gitchain-search
**URL:** https://gitchain-search.[account].workers.dev
**Custom domain:** [if configured]

## Endpoints
| Endpoint | Method | Cache TTL |
|----------|--------|-----------|
| /search | GET | 1 hour |
| /product/{id} | GET | 24 hours |
| /status | GET | none |
| /catalog/{ns} | GET | 24 hours |

## Performance
- Edge locations: 300+
- Cache hit latency: <5ms
- Cache miss latency: <100ms
- Rate limit: 100 req/min/IP

## Next Steps
- Add custom domain: `api.gitchain.0711.io`
- Warm cache: `/gitchain-cloudflare:cache warm bosch`
- Monitor: Cloudflare Dashboard → Workers

Rules

• Always add CORS headers (allow all origins for public API)
• Always implement KV caching
• Always add rate limiting
• Include error handling for backend timeouts
• Log request metrics to Workers Analytics