MediaForge
Local-first batch pipeline for processing media assets
what it proves
Proves pipeline and batch-orchestration design: composable FFmpeg stages driven by declarative job configs, deterministic and fully offline. Docker is intentionally absent rather than claimed.
Config-driven local batch pipeline that turns repeated media preparation steps into a predictable plan: deterministic stage ordering, FFprobe and FFmpeg command construction, stable output paths and dry-run verification. The repository also includes CueBot, a Discord bot built on the same reusable media-core package. It runs entirely offline, demonstrating pipeline design and batch orchestration rather than downloading.
proof points
- Declarative job configs driving composable pipeline stages
- Unit tests around the pipeline stages, with CI passing on every push
- Designed to run fully offline, with no hidden service dependencies
- Public repository. The pipeline structure is inspectable
skills demonstrated
tech stack
engineering hygiene
- ✓ readme
- ✓ docs
- ✓ tests
- ✓ ci
- ✗ docker
Known gap: docker. Next step: add a concrete command runner for non-dry-run execution and write metadata JSON as a first-class pipeline artifact.
Guided CLI Simulator
Explore a read-only guided simulation of MediaForge's command-line interface or pipeline.
evidence
MediaForge launch
Announces the launch of MediaForge, a local-first TypeScript CLI processing pipeline featuring automated validation, dry-run dependency graphs, and automated testing hooks.
view on linkedinwhere to see it
Public repository. Read it directly: github.com/noel-q/mediaforge-cuebot