|
@@ -100,7 +100,7 @@ Note that it is also possible to [host the web client separately](#hosting-the-w
|
|
|
|
|
|
There are three options to get the files for the web client.
|
|
|
|
|
|
-1. Download one of the finished builds from the [Azure DevOps pipeline](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=11). You can download the build for a specific release by looking at the [branches tab](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=11&_a=summary&repositoryFilter=6&view=branches) of the pipelines page.
|
|
|
+1. Download one of the finished builds from the [Azure DevOps pipeline](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=27). You can download the build for a specific release by looking at the [branches tab](https://dev.azure.com/jellyfin-project/jellyfin/_build?definitionId=27&_a=summary&repositoryFilter=6&view=branches) of the pipelines page.
|
|
|
2. Build them from source following the instructions on the [jellyfin-web repository](https://github.com/jellyfin/jellyfin-web)
|
|
|
3. 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-web`
|
|
|
|
|
@@ -166,3 +166,5 @@ To instruct the server not to host the web content, there is a `nowebclient` con
|
|
|
switch `--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 seperately.
|