diff options
| -rw-r--r-- | README.md | 29 | ||||
| -rw-r--r-- | debian/changelog | 6 | ||||
| -rw-r--r-- | debian/control | 2 |
3 files changed, 28 insertions, 9 deletions
@@ -51,6 +51,10 @@ A package repository is available at https://repo.jellyfin.org. To use it: sudo apt install jellyfin ``` +### Unraid + +An Unraid Docker template is available. See [this documentation page](https://github.com/jellyfin/jellyfin/blob/master/unRaid/docker-templates/README.md) for details on installing it. + ## Building Jellyfin packages from source Jellyfin seeks to integrate build facilities for any desired packaging format. Instructions for the various formats can be found below. @@ -61,17 +65,26 @@ NOTE: When building from source, only cloning the full Git repository is support Debian build facilities are integrated into the repo at `debian/`. -1. Install the `dotnet-sdk-2.1` package via [Microsoft's repositories](https://dotnet.microsoft.com/download/dotnet-core/2.1). -2. Run `dpkg-buildpackage -us -uc`. -3. Install the resulting `jellyfin_*.deb` file on your system. +0. Install the `dotnet-sdk-2.1` package via [Microsoft's repositories](https://dotnet.microsoft.com/download/dotnet-core/2.1). +0. Run `dpkg-buildpackage -us -uc`. +0. Install the resulting `jellyfin_*.deb` file on your system. A huge thanks to Carlos Hernandez who created the original Debian build configuration for Emby 3.1.1. ### Windows (64 bit) + A pre-built windows installer will be available soon. Until then it isn't too hard to install Jellyfin from Source. -1. Install the dotnet core SDK 2.1 from [Microsoft's Webpage](https://dotnet.microsoft.com/download/dotnet-core/2.1) and [install Git for Windows](https://gitforwindows.org/) -2. Clone Jellyfin into a directory of your choice. `git clone https://github.com/jellyfin/jellyfin.git C:\Jellyfin` -3. From the Jellyfin directory you can use our Jellyfin build script. Call `Build-Jellyfin.ps1 -InstallFFMPEG` from inside the directory in a powershell window. Make sure you've set your executionpolicy to unsrestricted. If you want to optimize for your environment you can use the -WindowsVersion and -Architecture flags to do so, default is generic windows x64. The -InstallLocation flag lets you select where the compiled binaries go, default is `$Env:AppData\JellyFin-Server\` . The -InstallFFMPEG flag will automatically pull the stable FFMPEG binaries appropriate to your architecture (x86/x64 only for now) from [Zeranoe](https://ffmpeg.zeranoe.com/builds/), and then place them in your emby directory. -4. (Optional) Use [NSSM](https://nssm.cc/) to configure JellyFin to run as a service -5. Jellyfin is now available in the default directory (or the directory you chose). Assuming you kept the default directory, to start it from a powershell window run, `&"$env:APPDATA\Jellyfin-Server\EmbyServer.exe"`. To start it from CMD run, `%APPDATA%\Jellyfin-Server\EmbyServer.exe`
\ No newline at end of file +0. Install the dotnet core SDK 2.1 from [Microsoft's Webpage](https://dotnet.microsoft.com/download/dotnet-core/2.1) and [install Git for Windows](https://gitforwindows.org/) +0. Clone Jellyfin into a directory of your choice. + ``` + git clone https://github.com/jellyfin/jellyfin.git C:\Jellyfin + ``` +0. From the Jellyfin directory you can use our Jellyfin build script. Call `Build-Jellyfin.ps1 -InstallFFMPEG` from inside the directory in a powershell window. Make sure you've set your executionpolicy to unsrestricted. + + Additional flags: + * If you want to optimize for your environment you can use the `-WindowsVersion` and `-Architecture` flags to do so; the default is generic Windows x64. + * The `-InstallLocation` flag lets you select where the compiled binaries go; the default is `$Env:AppData\JellyFin-Server\` . + * The `-InstallFFMPEG` flag will automatically pull the stable ffmpeg binaries appropriate to your architecture (x86/x64 only for now) from [Zeranoe](https://ffmpeg.zeranoe.com/builds/) and place them in your Jellyfin directory. +0. (Optional) Use [NSSM](https://nssm.cc/) to configure JellyFin to run as a service +0. Jellyfin is now available in the default directory (or the directory you chose). Assuming you kept the default directory, to start it from a Powershell window, run, `&"$env:APPDATA\Jellyfin-Server\EmbyServer.exe"`. To start it from CMD, run, `%APPDATA%\Jellyfin-Server\EmbyServer.exe` diff --git a/debian/changelog b/debian/changelog index 9199f71fc..e41c6b8e6 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +jellyfin (3.5.2-1) unstable; urgency=medium + + * Add ffmpeg dependency and cleanup work + + -- Joshua Boniface <joshua@boniface.me> Tue, 11 Dec 2018 20:55:32 -0500 + jellyfin (3.5.2) unstable; urgency=medium * Rename from emby-server on version 3.5.2 diff --git a/debian/control b/debian/control index 7d1e5de38..41a491c08 100644 --- a/debian/control +++ b/debian/control @@ -12,6 +12,6 @@ Replaces: mediabrowser, emby, emby-server-beta, jellyfin-dev, emby-server Breaks: mediabrowser, emby, emby-server-beta, jellyfin-dev, emby-server Conflicts: mediabrowser, emby, emby-server-beta, jellyfin-dev, emby-server Architecture: all -Depends: ${shlibs:Depends}, ${misc:Depends}, at, libsqlite3-0, dotnet-runtime-2.1 +Depends: ${shlibs:Depends}, ${misc:Depends}, at, libsqlite3-0, dotnet-runtime-2.1, ffmpeg Description: Jellyfin is a home media server. It is built on top of other popular open source technologies such as Service Stack, jQuery, jQuery mobile, and Mono. It features a REST-based api with built-in documentation to facilitate client development. We also have client libraries for our api to enable rapid development. |