Overview
Live state of your collection database and the automated collector.
Drama Status
Completed — every planned episode is released & collected (URLs stored).
Ongoing — the platform is still releasing episodes; new ones are picked up automatically every day.
Ongoing — the platform is still releasing episodes; new ones are picked up automatically every day.
Language Coverage
Collection
Every collected drama — title, cover, categories, tags, synopsis, episode counts and per-episode playback URLs.
| Title | Lang | Status | Episodes | Paid | Categories | Updated | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
–
Collector
Automated sweep across every supported language — metadata + playback URLs straight into your SQL database.
Run Control
–
–
–
Daily schedule03:00 (systemd timer)
Auto-force scheduleevery 6h (00/06/12/18)
Auto-force status-
Languages this run–
Database–
Live Log
log tail appears here…
How it works
Each run discovers dramas from every catalog feed (trending, VIP, latest, for-you, rank, every category browse) per language, then collects each new drama: metadata plus a playback URL for every released episode — paid episodes included, unlocked via guest sessions.
Already-fresh dramas are skipped (refresh window), so re-runs only pick up new dramas and newly released episodes. CDN URL tokens expire after hours — the daily timer keeps them fresh automatically.
Everything is resume-safe: the SQL database is the state. Interrupted runs continue where they left off.
Export
Collector Settings
Saved to
collector/collector.json — applies to scheduled and manual runs. Precedence: CLI flags → this file → environment.Pick specific languages or All (15 supported). Discovery and collection run per language.
How deep to paginate each discovery feed. Higher = broader catalog coverage per run.
Re-collect dramas older than this. 24 h keeps URLs fresh and catches daily releases.
Parallel chapter fetches. Keep low (1–3) to stay friendly to the upstream WAF budget.
Pacing pause per worker between dramas.
Safety cap per run. 0 = collect everything discovered.
sqlite:path | mysql://user:pass@host/db | postgres://… — the dashboard reads the sqlite target.
API Playground
Live "Try It" for every endpoint — your dashboard login authorizes the calls. Heavy endpoints (chapters/all, stream) may take a few seconds on first hit.