From 2144038970bcad95cba982fc6aceba001d6c7a22 Mon Sep 17 00:00:00 2001 From: Filip Rojek Date: Thu, 17 Oct 2024 14:03:35 +0200 Subject: [PATCH] Rewrite title and description for jellyfin post --- content/posts/jellyfin.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/posts/jellyfin.md b/content/posts/jellyfin.md index 959a3a2..f1e3aaf 100644 --- a/content/posts/jellyfin.md +++ b/content/posts/jellyfin.md @@ -1,10 +1,9 @@ +++ -title = "Jellyfin" +title = "Host Jellyfin with Docker and Docker Compose" date = 2024-10-03 -description = "Hosting a Jellyfin Instance with Docker and Docker Compose" +description = "Set up a Jellyfin media server with Docker, including hardware transcoding, media management, and companion services like Jellyseerr and Jellystat." +++ -# Hosting a Jellyfin Instance with Docker and Docker Compose Running your own media server is a great way to have complete control over your media library, and Jellyfin is one of the best open-source media server solutions available today. With Docker and Docker Compose, you can efficiently manage and scale your Jellyfin instance, along with useful companion services like Jellyseerr and Jellystat for enhanced functionality. In this article, I’ll walk through my setup of a Jellyfin media server, hosted in Docker using Docker Compose. This assumes you already have Docker and Docker Compose installed and are comfortable with Linux environments. I’ll cover the configuration of Jellyfin, hardware transcoding, and the integration of supporting services like Jellyseerr and Jellystat to manage requests and track server statistics.