docs: add Cloudflare Worker edition documentation

- README.md: Added Worker deployment section, updated troubleshooting
  - Fix 1: Cloudflare Worker (best — free, works)
  - Fix 2: ScraperAPI (paid, 9/mo)
  - Fix 3: FlareSolverr (self-hosted)
  - Fix 4: Self-host API
  - Added Worker vs Vercel comparison table
- docs/architecture.md: Added Worker architecture section
  - Why Workers work (edge-to-edge bypass)
  - Worker runtime differences table
  - 15 Worker endpoints listed
  - Deploy instructions
- CHANGELOG.md: Added v2.3.1 entry for Worker edition
This commit is contained in:
Shinei Nouzen
2026-07-02 09:34:18 +05:30
parent 3f667fe87f
commit 2c97ca2dd8
3 changed files with 129 additions and 3 deletions
+30
View File
@@ -1,5 +1,35 @@
# Changelog
## v2.3.1
### Cloudflare Worker Edition — Streaming Bypasses Cloudflare
#### New: `worker.js` (Cloudflare Worker)
- Full API running on Cloudflare's edge network
- **Streaming endpoints work** — edge-to-edge requests bypass bot detection
- Zero cold starts, 100K free requests/day
- No npm dependencies (native `fetch` + `DecompressionStream`)
- 15 endpoints: search, trending, info, episodes, watch, genres, random
#### Why Workers Work
```
Vercel (datacenter) → miruro.to → Cloudflare blocks ❌
Worker (edge) → miruro.to → Cloudflare trusts itself ✅
```
#### Deploy
```bash
npm install -g wrangler
wrangler login
wrangler deploy worker.js --name miruroapi
```
#### Files Changed
- `worker.js` — Cloudflare Worker implementation (885 lines)
- `README.md` — Added Worker deployment section, updated troubleshooting
- `docs/architecture.md` — Added Worker architecture section
---
## v2.3.0
### Self-Healing Fallback System — Auto-Recovery from Cloudflare Blocks