ArchiveorgSoftwareThe Free Software Media System The Free Software Media System Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it. We welcome anyone who is interested in joining us in our quest!For further details, please see our documentation page[1]. To receive the latest updates, get help with Jellyfin, and join the community, please visit one of our communication channels[2]. For more information about the project, please see our about page[3].Want to get started?Choose from Prebuilt Packages or Build from Source, then see our quick start guide.[4][5][6]Something not working right?Open an Issue on GitHub.[7]Want to contribute?Check out our documentation for guidelines.[8]New idea or improvement?Check out our feature request hub.[9]Most of the translations can be found in the web client but we have several other clients that have missing strings. Translations can be improved very easily from our Weblate[10] instance. Look through the following graphic to see if your native language could use some work! Jellyfin ServerThis repository contains the code for Jellyfin's backend server. Note that this is only one of many projects under the Jellyfin GitHub organization[11] on GitHub. If you want to contribute, you can start by checking out our documentation[12] to see what to work on.Server DevelopmentThese instructions will help you get set up with a local development environment in order to contribute to this repository. Before you start, please be sure to completely read our guidelines on development contributions[13]. Note that this project is supported on all major operating systems except FreeBSD, which is still incompatible.PrerequisitesBefore the project can be built, you must first install the .NET Core 3.1 SDK[14] on your system.Instructions to run this project from the command line are included here, but you will also need to install an IDE if you want to debug the server while it is running. Any IDE that supports .NET Core development will work, but two options are recent versions of Visual Studio[15] (at least 2017) and Visual Studio Code[16].Cloning the RepositoryAfter dependencies are installed you will need to clone a local copy of this repository. If you just want to run the server from source you can clone this repository directly, but if you are intending to contribute code changes to the project, you should set up your own fork[17] of the repository. The following example shows how you can clone the repository directly over HTTPS.bashgit clone the Web ClientThe server is configured to host the static files required for the web client[18] in addition to serving the backend by default. Before you can run the server, you will need to get a copy of the web client since they are not included in this repository directly.Note that it is also possible to host the web client separately[19] from the web server with some additional configuration, in which case you can skip this step.There are three options to get the files for the web client.Download one of the finished builds from the Azure DevOps pipeline[20]. You can download the build for a specific release by looking at the branches tab[21] of the pipelines page.Build them from source following the instructions on the jellyfin-web repository[22]Get the pre-built files from an existing installation of the server. For example, with a Windows server installation the client files are located at C:\Program Files\Jellyfin\Server\jellyfin-webOnce you have a copy of the built web client files, you need to copy them into a specific directory. /Mediabrowser.WebDashboard/jellyfin-webAs part of the build process, this folder will be copied to the build output directory, where it can be accessed by the server.Running The ServerThe following instructions will help you get the project up and running via the command line, or your preferred IDE.Running With Visual StudioTo run the project with Visual Studio you can open the Solution (.sln) file and then press F5 to run the server.Running With Visual Studio CodeTo run the project with Visual Studio Code you will first need to open the repository directory with Visual Studio Code using the Open Folder... option.Second, you need to install the recommended extensions for the workspace[23]. Note that extension recommendations are classified as either "Workspace Recommendations" or "Other Recommendations", but only the "Workspace Recommendations" are required.After the required extensions are installed, you can can run the server by pressing F5.Running From The Command LineTo run the server from the command line you can use the dotnet run command. The example below shows how to do this if you have cloned the repository into a directory named jellyfin (the default directory name) and should work on all operating systems.bashcd jellyfin # Move into the repository directorydotnet run --project Jellyfin.Server # Run the server startup projectA second option is to build the project and then run the resulting executable file directly. When running the executable directly you can easily add command line options. Add the --help flag to list details on all the supported command line options.Build the projectbashdotnet build # Build the projectcd bin/Debug/netcoreapp3.1 # Change into the build output directoryExecute the build output. On Linux, Mac, etc. use ./jellyfin and on Windows use jellyfin.exe.Running The TestsThis repository also includes unit tests that are used to validate functionality as part of a CI pipeline on Azure. There are several ways to run these tests.Run tests from the command line using dotnet testRun tests in Visual Studio using the Test Explorer[24]Run individual tests in Visual Studio Code using the associated CodeLens annotation[25]Advanced ConfigurationThe following sections describe some more advanced scenarios for running the server from source that build upon the standard instructions above.Hosting The Web Client SeparatelyIt is not necessary to host the frontend web client as part of the backend server. Hosting these two components separately may be useful for frontend developers who would prefer to host the client in a separate webpack development server for a tighter development loop. See the jellyfin-web[26] repo for instructions on how to do this.To instruct the server not to host the web content, there is a nowebclient configuration flag that must be set. This can specified using the command lineswitch --nowebclient or the environment variable JELLYFIN_NOWEBCONTENT=true.Since this is a common scenario, there is also a separate launch profile defined for Visual Studio called Jellyfin.Server (nowebcontent) that can be selected from the 'Start Debugging' dropdown in the main toolbar.NOTE: The setup wizard can not be run if the web client is hosted separately. To restore the repository download the bundle wget and run: git clone jellyfin-jellyfin_-_2020-09-15_17-17-00.bundle Source:[27]Uploader: jellyfin[28]Upload date: 2020-09-15 References^ our documentation page (^ one of our communication channels (^ about page (^ Prebuilt Packages (^ Build from Source (^ quick start guide (^ Issue (^ our documentation for guidelines (^ feature request hub (^ Weblate (^ organization (^ documentation (^ guidelines on development contributions (^ .NET Core 3.1 SDK (^ Visual Studio (^ Visual Studio Code (^ set up your own fork (^ web client (^ host the web client separately (^ Azure DevOps pipeline (^ branches tab (^ jellyfin-web repository (^ install the recommended extensions for the workspace (^ Test Explorer (^ CodeLens annotation (^ jellyfin-web (^ (^ jellyfin (

weiterlesen: RSS Quelle öffnen