Docker Config
Service-level Docker reference for ports, responsibilities, and stack boundaries.
by @saifyxpro
Core stack
The Docker infrastructure lives under infra/docker.
Current core services are centered on:
| Service | Default role | Typical port |
|---|---|---|
| PostgreSQL | persistent app state | 5432 |
| Redis | queue and crawl infrastructure | 6379 |
| API | backend HTTP and MCP | 8000 |
| Worker | queued background jobs | none exposed |
| Web | dashboard and playground | 3000 |
| HTML-to-Markdown | content extraction helper | 8081 |
What Docker is best at here
- repeatable service boot
- consistent infrastructure across operators
- faster onboarding for self-hosted users
- cleaner separation between app runtime and dependencies
What still needs attention
Depending on your exact deployment, YouTube workflows may still rely on a separately managed yt-engine process and a correct YT_ENGINE_URL.
Compose usage
The safe current compose path is:
Volumes and persistence
You should treat these as persistent:
- PostgreSQL data
- Redis if you depend on durable queue state
- application-managed runtime data like profiles or temp artifacts, depending on your deployment policy
Operational advice
- use Docker for infrastructure even if you prefer local app processes
- keep environment files outside image definitions
- document any port changes together with
NEXT_PUBLIC_API_URL,FRONTEND_URL, and service URLs