Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sailing:jellyfin [2023/12/05 19:46] – willy | sailing:jellyfin [2024/02/27 12:37] (current) – removed willy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Prev to: [[sailing: | ||
- | Next to: [[sailing: | ||
- | ---- | ||
- | ====== JellyFin ====== | ||
- | |||
- | [[https:// | ||
- | |||
- | There are other options. At least the main two are Emby and Plex. Emby actually was open-source too until they decided to close up the code and JellyFin was born from it's fork. Plesk is a different solution, proprietary, | ||
- | |||
- | A brief summary: | ||
- | * JellyFin is open-source, | ||
- | * Emby used to be open-source, | ||
- | * Plex is a proprietary solution that uses it's own servers to stream to you your collection. It's a hard pass for me. | ||
- | |||
- | ===== Installation ===== | ||
- | |||
- | |||
- | You are lucky and the JellyFin mediaserver can be easily installed on Gentoo linux. You need to unmask it first: | ||
- | <code bash> | ||
- | > echo www-apps/ | ||
- | </ | ||
- | |||
- | then emerge it: | ||
- | <code bash> | ||
- | > emerge -v jellyfin | ||
- | </ | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | then we can emerge it. You want to add it to the " | ||
- | |||
- | Configuration phase | ||
- | |||
- | Now, JellyFin Gentoo default setup locates server directories under /var: | ||
- | |||
- | the data folder under /var/lib | ||
- | the cache folder under / | ||
- | the configuration folder under / | ||
- | the logs folder under / | ||
- | |||
- | which i don't like for a few reasons like: | ||
- | |||
- | this will clutter and fill the Gentoo installation disk (/dev/sda) | ||
- | this will NOT survive a /dev/sda disk crash (which is not RAID-1) | ||
- | this will not be consistent: i want to have all database and data in the same RAID | ||
- | |||
- | to fix this, move those to / | ||
- | |||
- | > mv / | ||
- | > mv / | ||
- | > mv / | ||
- | > mv / | ||
- | |||
- | in this case, differently from the *Arr' | ||
- | |||
- | # This is the directory that will hold all Jellyfin data, and is also used as a default base directory for some other paths below. | ||
- | JELLYFIN_DATA_DIR=/ | ||
- | |||
- | # This is the directory where the Jellyfin logs will be stored. | ||
- | JELLYFIN_LOG_DIR=/ | ||
- | |||
- | # This is the directory containing the server cache. | ||
- | JELLYFIN_CACHE_DIR=/ | ||
- | |||
- | # This is the directory containing the server configuration files. | ||
- | JELLYFIN_CONFIG_DIR=/ | ||
- | |||
- | This will move the server data folder on the RAID, there is not need to link them back here. | ||
- | |||
- | Startup phase | ||
- | |||
- | Well, it's time to fire up the server (and set it up for autostart on reboot): | ||
- | |||
- | > rc-update add jellyfin default | ||
- | > / | ||
- | |||
- | This will add the server to your startup and will also start it right now. At this point you should login to it and configure it trough the web GUI. If you are local to the network, you can fire up your browser to http:// | ||
- | |||
- | You should NOT use the server endpoint directly on you home network without a reverse-proxy, | ||
- | Securization | ||
- | |||
- | On the Jellyfin web gui, open the Dashboard and go to Networking. Here set 127.0.0.1 as bind to local network address, and also add /jellyfin as base URL. You will need to restart the service now. You will be able to access the service only from the server with the base URL. Point your browser to http:// | ||
- | |||
- | ---- | ||
- | Next to: [[sailing: | ||
- | |||
- | Prev to: [[sailing: |