mirror of
https://github.com/jellyfin/jellyfin.org.git
synced 2024-10-06 19:03:28 +00:00
Merge pull request #748 from jellyfin/nvv-mdx-3
Fix MDX 3 issues in markdown content
This commit is contained in:
Tim Eisele
GitHub
commit
e36b446ed8
@ -16,7 +16,7 @@ For a brief TL;DR: for most users of our stable releases, not much will change,
|
||||
|
||||
### Split Builds
|
||||
|
||||
The first main component of the packaging changes is split builds. Previously, we were relying on some serious hackery in order to build both the Web UI (<https://github.com/jellyfin/jellyfin-web>) and Server (<https://github.com/jellyfin/jellyfin>) and combine them into one package. Ultimately, with the sheer number of changes in both repositories and speed at which updates happen, along with our eventual goal to decouple the two from each other for releases, this sort of solution had reached its limits. This is perhaps best exemplified by the mostly-unseen work I had to do to get 10.5.4 and 10.5.5 to build at all.
|
||||
The first main component of the packaging changes is split builds. Previously, we were relying on some serious hackery in order to build both the Web UI ([https://github.com/jellyfin/jellyfin-web](https://github.com/jellyfin/jellyfin-web)) and Server ([https://github.com/jellyfin/jellyfin](https://github.com/jellyfin/jellyfin)) and combine them into one package. Ultimately, with the sheer number of changes in both repositories and speed at which updates happen, along with our eventual goal to decouple the two from each other for releases, this sort of solution had reached its limits. This is perhaps best exemplified by the mostly-unseen work I had to do to get 10.5.4 and 10.5.5 to build at all.
|
||||
|
||||
With split packages, the two repositories are now built completely independently for all platforms. If you build the `jellyfin-web` repository, you get out a Docker image, `.deb` packages, `.rpm` packages, or a `.tar.gz` archive that just contains the Web UI. Similarly, if you build the `jellyfin` repository, you get out the various Docker, `.deb`, `.rpm`, `.tar.gz`, and `.zip` archives you know and love.
|
||||
|
||||
|
||||
@ -53,9 +53,9 @@ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 1DE21A7B
|
||||
|
||||
**Please ensure you refresh the key before December 15th, or you will find that `apt update` no longer works!**
|
||||
|
||||
GitHub Issue for reference: <https://github.com/jellyfin/jellyfin/issues/4528>
|
||||
GitHub Issue for reference: [https://github.com/jellyfin/jellyfin/issues/4528](https://github.com/jellyfin/jellyfin/issues/4528)
|
||||
|
||||
Reddit thread for reference: <https://www.reddit.com/r/jellyfin/comments/jz6u9o/debian_ubuntu_repo_users_our_key_is_expiring/>
|
||||
Reddit thread for reference: [https://www.reddit.com/r/jellyfin/comments/jz6u9o/debian_ubuntu_repo_users_our_key_is_expiring/](https://www.reddit.com/r/jellyfin/comments/jz6u9o/debian_ubuntu_repo_users_our_key_is_expiring/)
|
||||
|
||||
Thanks,
|
||||
Joshua
|
||||
|
||||
@ -270,7 +270,7 @@ The main locations are `/archive`, `/releases`, and `/master`. The first contain
|
||||
|
||||
Next is the main Mirrorbits handler. The forwarding is based off the file extension of the requested file. Thus, when loading, e.g. the PHP index pages, the requests are not forwarded; only requests for the listed file types are forwarded on to the Mirrorbits process to be distributed to mirrors.
|
||||
|
||||
The next 3 options are for Mirrorbits status pages, which provide information on the currently available mirrors. For any file (e.g. <https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb>), one can append the `/mirrorlist` or `/mirrorinfo` locations to show information about the available mirrors. Try it yourself: <https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb/mirrorlist>. Finally the `/mirrorstats` page, whether on a file or at the root of the domain (<https://repo.jellyfin.org/mirrorstats>) shows the current status of the mirrors in general, including if any are offline.
|
||||
The next 3 options are for Mirrorbits status pages, which provide information on the currently available mirrors. For any file (e.g. [https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb](https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb)), one can append the `/mirrorlist` or `/mirrorinfo` locations to show information about the available mirrors. Try it yourself: [https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb/mirrorlist](https://repo.jellyfin.org/releases/server/debian/stable/meta/jellyfin_10.7.2-1_all.deb/mirrorlist). Finally the `/mirrorstats` page, whether on a file or at the root of the domain ([https://repo.jellyfin.org/mirrorstats](https://repo.jellyfin.org/mirrorstats)) shows the current status of the mirrors in general, including if any are offline.
|
||||
|
||||
All together, these NGiNX configs provide the foundation for Mirrorbits to work, and this was the part that actually took the longest. Thanks to [@PalinuroSec](https://github.com/PalinuroSec) on GitHub for his [fantastic example gist](https://gist.github.com/PalinuroSec/f0bfb815240573ab1b0b58f3c76620d4).
|
||||
|
||||
|
||||
@ -351,6 +351,6 @@ A point-form list of (some of) the changes compiled by the team is:
|
||||
|
||||
## Translations
|
||||
|
||||
Thanks to the many dozens of generous volunteers over at our Weblate (<https://translate.jellyfin.org>), thousands of new translations are available in Jellyfin 10.8.0 for over 3 dozen languages.
|
||||
Thanks to the many dozens of generous volunteers over at our Weblate ([https://translate.jellyfin.org](https://translate.jellyfin.org)), thousands of new translations are available in Jellyfin 10.8.0 for over 3 dozen languages.
|
||||
|
||||
Happy watching!
|
||||
|
||||
@ -281,11 +281,11 @@ There are some known upstream Linux Kernel and firmware issues that can affect t
|
||||
|
||||
1. Intel Gen 11 [**Jasper Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128823/products-formerly-jasper-lake.html) and [**Elkhart Lake**](https://ark.intel.com/content/www/us/en/ark/products/codename/128825/products-formerly-elkhart-lake.html) platforms (e.g. N5095, N5105, N6005, J6412) have quirks when using video encoders on Linux. The [Low-Power Encoding](/docs/general/administration/hardware-acceleration/intel#low-power-encoding) mode MUST be configured and enabled for correct VBR and CBR bitrate control that is required by Jellyfin.
|
||||
|
||||
- Ticket: <https://gitlab.freedesktop.org/drm/intel/-/issues/8080>
|
||||
- Ticket: [https://gitlab.freedesktop.org/drm/intel/-/issues/8080](https://gitlab.freedesktop.org/drm/intel/-/issues/8080)
|
||||
|
||||
2. The default kernel 5.15 that comes with Ubuntu 22.04 LTS has a regression on Intel Gen 11 graphics (ICL, JSL and EHL) that prevent you from using the Low-Power encoding mode. Linux 5.16+ is not affected.
|
||||
|
||||
- Ticket: <https://gitlab.freedesktop.org/drm/intel/-/issues/4067>
|
||||
- Ticket: [https://gitlab.freedesktop.org/drm/intel/-/issues/4067](https://gitlab.freedesktop.org/drm/intel/-/issues/4067)
|
||||
|
||||
- Fixed by: [drm/i915/gen11: Moving WAs to icl_gt_workarounds_init()](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52255ef662a5d490678fbad64a735f88fcba564d)
|
||||
|
||||
@ -303,7 +303,7 @@ There are some known upstream Linux Kernel and firmware issues that can affect t
|
||||
|
||||
3. The kernel range from 5.18 to 6.1.3 have an issue that locks up and resets the i915 kernel driver when using OpenCL based HDR/DV tone-mapping. Linux 5.18-, 6.0.18+, 6.1.4+ are not affected.
|
||||
|
||||
- Ticket: <https://gitlab.freedesktop.org/drm/intel/-/issues/7627>
|
||||
- Ticket: [https://gitlab.freedesktop.org/drm/intel/-/issues/7627](https://gitlab.freedesktop.org/drm/intel/-/issues/7627)
|
||||
|
||||
- Fixed by: [drm/i915: improve the catch-all evict to handle lock contention](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3f882f2d4f689627c1566c2c92087bc3ff734953)
|
||||
|
||||
|
||||
@ -181,13 +181,13 @@ Root permission is required.
|
||||
|
||||
3. Install the NVIDIA proprietary driver by following these links. Then install two extra packages for NVENC and NVDEC support:
|
||||
|
||||
- On Debian: <https://wiki.debian.org/NvidiaGraphicsDrivers>
|
||||
- On Debian: [https://wiki.debian.org/NvidiaGraphicsDrivers](https://wiki.debian.org/NvidiaGraphicsDrivers)
|
||||
|
||||
```shell
|
||||
sudo apt update && sudo apt install -y libnvcuvid1 libnvidia-encode1
|
||||
```
|
||||
|
||||
- On Ubuntu: <https://help.ubuntu.com/community/NvidiaDriversInstallation>
|
||||
- On Ubuntu: [https://help.ubuntu.com/community/NvidiaDriversInstallation](https://help.ubuntu.com/community/NvidiaDriversInstallation)
|
||||
|
||||
:::note
|
||||
|
||||
@ -247,7 +247,7 @@ Root permission is required.
|
||||
|
||||
2. Install the NVIDIA proprietary driver by following the link. Then install an extra package for NVENC and NVDEC support:
|
||||
|
||||
- <https://wiki.archlinux.org/title/NVIDIA#Installation>
|
||||
- [https://wiki.archlinux.org/title/NVIDIA#Installation](https://wiki.archlinux.org/title/NVIDIA#Installation)
|
||||
|
||||
```shell
|
||||
sudo pacman -Syu nvidia-utils
|
||||
@ -320,7 +320,7 @@ Root permission is required.
|
||||
|
||||
2. Install the NVIDIA Container Toolkit on the host system by following this link:
|
||||
|
||||
- <https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#installation-guide>
|
||||
- [https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#installation-guide](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html#installation-guide)
|
||||
|
||||
3. Use the Docker command line **or** docker-compose:
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ Jellyfin is an entirely volunteer-driven project, so until a developer is able a
|
||||
We track community feature requests on [our Fider instance](https://features.jellyfin.org), so please check that out, upvote the features you like, and add your own requests. Note that the Fider does not guarantee prioritization, but instead provides developers a way of seeing what features might be popular to decide whether to work on them or not. This does unfortunately mean that even highly-soughtafter features might not be implemented until someone both interested and able to work on them comes along.
|
||||
If you're a developer and are interested in helping out, [please hack away](/docs/general/contributing) and let us know [on Matrix](/docs/general/getting-help) so we can help.
|
||||
|
||||
## When will release {X} happen? When will feature {X} be available?
|
||||
## When will release \{X} happen? When will feature \{X} be available?
|
||||
|
||||
We make releases only when the team feels that it is ready, to provide our users with the best and most stable experience we can.
|
||||
To that end, releases happen when we feel there has been sufficient testing without new issues being found.
|
||||
|
||||
@ -48,7 +48,7 @@ This will delete all settings and user information. This applies for the .app pa
|
||||
2. Extract it into the Applications folder
|
||||
3. Open Terminal and type `cd` followed with a space then drag the jellyfin folder into the terminal.
|
||||
4. Type `./jellyfin` to run jellyfin.
|
||||
5. Open your browser at <http://localhost:8096>
|
||||
5. Open your browser at [http://localhost:8096](http://localhost:8096)
|
||||
|
||||
Closing the terminal window will end Jellyfin. Running Jellyfin in screen or tmux can prevent this from happening.
|
||||
|
||||
@ -59,7 +59,7 @@ Closing the terminal window will end Jellyfin. Running Jellyfin in screen or tmu
|
||||
1. Extract the latest version into Applications
|
||||
1. Open Terminal and type `cd` followed with a space then drag the jellyfin folder into the terminal.
|
||||
1. Type `./jellyfin` to run jellyfin.
|
||||
1. Open your browser at <http://localhost:8096>
|
||||
1. Open your browser at [http://localhost:8096](http://localhost:8096)
|
||||
|
||||
**Uninstalling the Portable Version**
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ Using the Advanced/Service mode may experience FFmpeg hardware acceleration issu
|
||||
2. Run the installer.
|
||||
3. (Optional) When installing as a service (not recommended), pick the service account type.
|
||||
4. If everything was completed successfully, Jellyfin is now running.
|
||||
5. Open your browser at <http://your_local_IP_address:8096> to finish setting up Jellyfin.
|
||||
5. Open your browser at [http://your_local_IP_address:8096](http://your_local_IP_address:8096) to finish setting up Jellyfin.
|
||||
|
||||
**Update**
|
||||
|
||||
|
||||
@ -267,7 +267,7 @@ Enables audio scrobbling to Last.FM as well as a metadata fetcher source.
|
||||
|
||||
#### Kinopoisk metadata plugin
|
||||
|
||||
Fetches metadata from <https://kinopoisk.ru>. This site is popular in the Russian-speaking community and contains almost no English-language information. Can provide movies and series rating, description, actors and staff, trailers and so on.
|
||||
Fetches metadata from [https://kinopoisk.ru](https://kinopoisk.ru). This site is popular in the Russian-speaking community and contains almost no English-language information. Can provide movies and series rating, description, actors and staff, trailers and so on.
|
||||
|
||||
**Links:**
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user