How neerajrao23/mini-pipeline works
Project type and purpose
• This is a containerized, dual-microservice video-processing pipeline built with Node.js and Docker Compose.
• One service (“api”) handles video ingestion, processing, and asynchronous callbacks. The other (“interface”) exposes a web UI, handles callbacks, stores results, and renders them via EJS.
File structure
• Top-level:
• docker-compose.yml – orchestrates both services
• .env examples – environment variable templates
• api/
• Dockerfile, .env, package.json, server.js
• Exposes REST endpoints on port 8000
• interface/
• Dockerfile, package.json, index.js
• public/ (static assets), views/ (EJS templates)
• Exposes port 4000, handles incoming callback posts, writes received.json, serves UI
README for key insights
• Features: file upload & remote-URL input, webhook callbacks, persistent storage (received.json), health checks, Docker volume mapping
Detail
• Every REST endpoint and method
• Environment variables usage via .env files
• Volume mounts under each service
• Host access (host.docker.internal for callbacks in URL mode)
• Both file-upload and URL-fetch flows