Tooling

Git Workflow

All repos follow the same PR flow:

  1. Branch from main
  2. Open PR on GitHub
  3. Greptile auto-reviews the PR
  4. Auto-merge at score 4/5+ (pr-auto-merge cron on PolicyJar)
  5. Deploy triggers automatically (or manually via Wrangler)

Git config: user coygg, email me@coy.gg

OpenNext (@opennextjs/cloudflare)

Build tool that compiles Next.js apps to run on Cloudflare Workers. Used by Ad Analyzer, Creative Engine, Copy System, and Product Research.

Converts Next.js server-side rendering, API routes, and middleware into Worker-compatible code.

Wrangler

Cloudflare CLI for managing Workers, D1, R2, Pages, Vectorize.

Common commands:

  • npx wrangler pages deploy out --project-name=<name> - Deploy Pages project
  • npx wrangler d1 execute <db> --command "SQL" - Run D1 queries
  • npx wrangler r2 object put <bucket>/<key> --file <path> - Upload to R2
  • npx wrangler tail - Stream Worker logs

CamoFox

Anti-detection browser proxy on Fly.io. Primary tool for all web fetching and Google searching.

  • Scrape: POST https://camofox.fly.dev/scrape with {"url": "..."}
  • Render: POST https://camofox.fly.dev/render for JS-rendered pages
  • Proxy fetch: POST https://camofox.fly.dev/proxy-fetch for residential proxy
  • Auth header: x-api-key: <key>

Schematron (Inference.net)

Structured HTML-to-JSON extraction. Takes raw HTML and returns clean structured data.

Docker Dev Container

  • Container: coy-dev (Ubuntu 24.04)
  • SSH: ssh dev@localhost -p 2222
  • Mounts: C:\Users\me\Projects to /home/dev/projects/
  • Rule: Always use Docker for file edits to avoid CRLF issues

Build & Deploy Commands

Project Command
Wiki npm run build && npx wrangler pages deploy out --project-name=coydevs-wiki
PolicyJar Push to master, Vercel auto-deploy
CamoFox flyctl deploy
All Cloudflare apps npx wrangler deploy (Workers) or npx wrangler pages deploy (Pages)