jellyfin mit Homebrew Cask installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Projektgeschichte

Jellyfin began in early December 2018 after Emby announced that its 4.x release would be closed source. The founders forked the legally available Emby repositories, renamed the project, and continued development with a free-software ethos.

The server descends from Emby 3.5.2 and was ported to .NET Core for cross-platform support. Development is coordinated by a worldwide volunteer community that maintains the server, web interface, documentation, translations, plugins, and clients.

Adoptionsgeschichte

Jellyfin grew as a volunteer-run, fully free-software alternative to Emby and Plex. Its server is paired with web, desktop, mobile, television, and other clients maintained across the Jellyfin organization.

Its no-premium-feature model and support for native packages, containers, NAS platforms, and multiple operating systems have made it a prominent self-hosted media-server choice.

Wie es verwendet wird

Administrators install the Jellyfin server, add media libraries, create local users, and stream content through web or native clients. The server can direct-play compatible media or transcode it for client and network constraints.

Common deployments range from a macOS desktop application to Linux services, containers, NAS systems, and home servers. Configuration is primarily managed through the administrator dashboard, with startup paths, logging, networking, and advanced database behavior available through files, environment variables, and command-line options.

Warum Paket-Nerds sich dafür interessieren

Jellyfin is a major example of a community preserving a self-hosted application after its upstream moved toward proprietary development. Package maintainers handle a substantial .NET server, web client, FFmpeg integration, hardware acceleration, and a wide client ecosystem.

Administrators value that the complete server remains auditable and self-hostable without license-gated features. Its explicit data, configuration, cache, and log paths also make it suitable for declarative deployments, containers, and backup automation.

Zeitleiste

• December 2018: The Jellyfin project began as a fork of Emby 3.5.2.
• 2018 onward: The project expanded into a volunteer-maintained server, client, plugin, translation, and documentation ecosystem.
• 10.11: Jellyfin added a built-in server backup facility.

Related projects

• Emby 3.5.2 is Jellyfin's direct technical ancestor.
• Plex and modern Emby are the principal proprietary media-server alternatives identified by the project.
• Jellyfin Web and the various Jellyfin client projects provide interfaces to the core server.
• FFmpeg supplies media probing and transcoding capabilities.

Quellen

• https://jellyfin.org/docs/
• https://jellyfin.org/docs/general/about/
• https://jellyfin.org/docs/general/administration/configuration/
• https://jellyfin.org/docs/general/installation/macos/