DramaBox — Collection Dashboard

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.

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)

Languages this run–

Database–

Live Log

log tail appears here…

How it works

Each run discovers dramas from every catalog feed (trending, 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.

Collection is progressive and gentle: one catalog page per cycle, every drama verified before storing (playable links are kept as-is; only dead links are re-fetched). Sessions rotate automatically and the engine backs off politely whenever challenged — it never bursts.

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

⬇ Full JSON ⬇ Current language

MySQL writeback

Configure the destination database and inspect its tables before writing verified OSS links and drama information.

Database host

Database port

Database name

Database user

Database password

Credentials are encrypted on the server and never returned to this page.

To keep saved credentials, leave both credential fields blank.

Write a completed OSS drama

Reads metadata.json from OSS and checks every file size and SHA256 before committing drama information and new public object URLs. Private objects still require access authorization.

Query language

Original drama ID

Alibaba Cloud OSS

Save your bucket settings, then test a temporary object upload, read and cleanup.

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.