How fallenbagel/jellyseerr works
Based on our analysis, Jellyseerr is a full‐stack, open–source media request management application that integrates with several media servers (Jellyfin, Plex, Emby) and external services like Sonarr and Radarr. Its purpose is to offer a unified, user–friendly interface for requesting media (movies, TV shows, etc.) with robust backend API support, a web–based front end (built in Next.js with a well–structured “src” directory), and a set of deployment assets (Dockerfiles, Helm charts, Kubernetes manifests) ensuring containerized and cloud–compatible deployments.
Main Components
• Frontend: Represented by the “src” directory; it contains pages, components, contexts, hooks, styles, and i18n resources. This layer handles user interface (views, routing, internationalization) and interacts with the backend API.
• Backend/API Server: The “server” directory includes API routes, business logic (controllers, interfaces, and various libraries such as scanning, email, notifications, and settings). It handles authentication, request management, and integrations with external services.
• Database Layer: Support for PostgreSQL and SQLite is apparent in the migration scripts (under server/migration). This component is responsible for persisting users, media requests, settings, and logs.
• Deployment and DevOps: Note the Dockerfiles (Dockerfile, Dockerfile.local), Helm charts (under charts), and GitHub workflows (under .github/workflows) that indicate CI/CD, testing (e.g., Cypress tests in the “cypress” folder) and deployment strategies, which interact with both the code and the production environment.
Relationships & Interactions
• The Frontend makes HTTP calls (via RESTful API endpoints) to the Backend, retrieving data, sending requests, and handling user sessions.
• The Backend orchestrates business logic, processes requests, communicates with one or more databases (PostgreSQL or SQLite), and integrates with external services (media servers and notification agents).
• Data flows from the user to the frontend, which in turn communicates with the server; the server then reads/writes to the database and calls out to external media APIs.
• CI/CD pipelines (GitHub workflows, Docker, Helm) manage builds, tests, and deployments, ensuring that each component is reliably packaged and released to production.
Architectural Patterns & Design Principles
• Separation of concerns: Clear division between frontend “view” (Next.js pages and components), backend routing and business logic, and database persistence.
• Modular design: The “server” directory is organized by domain (e.g., routes, entity, library, notifications, migrations) suggesting a modular approach—with each integration (Plex, Jellyfin, Sonarr, etc.) encapsulated in its own module.
• Extensibility: The structured components in both frontend and backend allow for additional integrations or features.
• Container–based deployment: The presence of Dockerfiles, Helm charts, and Kubernetes configurations implies that containers play a central role in deployment architecture.
Relevant Technologies & Frameworks
• Frontend: Next.js, React, TypeScript, along with state management via React contexts and hooks.
• Backend: Node.js with TypeScript, Express (assumed from “server/middleware”, “server/routes”), and various libraries handling database migrations, API interactions, and email/notification templating.
• Database: PostgreSQL and SQLite.
• Deployment: Docker, Docker Compose, Kubernetes (Helm charts) and CI pipelines via GitHub Actions.
• Testing: Cypress for end–to–end testing as seen in the “cypress” directory.