• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle

  • Depends what you want to play it on. In my house we have:

    3 laptops 2 tablets 2 mobile phones (1 android, 1 iPhone) TV

    Not all these devices support local storage for music and it’s a pain to sync files between them. With Jellyfin the complete library is in one location with a consistent interface. It can also be made available remotely if I choose.


  • Ok. I missed which sub I was in, sorry. There is a Linux desktop Jellyfin app but I haven’t used it myself. In my own case I am running Jellyfin on Linux. I use various clients, including web browser (laptop), Android and Roku (TV) and find it works really well. In the past I had tried with the ‘connect directly to the server’ route with XBMC (as Kodi was called then) and it never worked well, with similar issues those described in other comments.




  • I think you’re missing a key area here. The original Mozilla product was Netscape- a commercial combined web browser and email client. There used to be a number of commercial competitors in the space, e.g. Opera, Eudora, etc. Microsoft killed that market in the 1990’s.

    I struggle to see how any organisation could make money out of giving away a product that costs money to produce and promote. You’ve suggested they could have been Proton but that’s a completely different sector. We could just as easily have suggested they could have been Twitter, WhatsApp or Instagram.


  • We’re going to need to know as a minimum:

    • Linux distribution and version
    • Jellyfin install method and version
    • what you have already tried- not sure where all those flags are coming from

    I would also support the comments here recommending that you use docker. There’s only a small number of Linux distributions and versions where a distribution package installation of jellyfin is fully supported, but even then what you need to do varies across each one. All Linux distributions and versions support docker and the process is essentially the same for all of them.


  • Ok, aside from Android, I’ve yet to see any serious usage of SELinux in the real world and I’ve been working on cloud tech for years. Acknowledged issues such as complexity aside, it’s really just that much less relevant in a modern, single purpose environment such as Docker/kubernetes/cloud functions/etc




  • Coming from what looks to me like a different perspective to many of the commenters here (Disclosure I am a professional platform engineer):

    If you are already scripting your setups then yes you should absolutely learn/use Ansible. The key reasons are that it is robust, explicit, and repeatable- doesn’t matter whether that’s the same host multiple times or multiple hosts. I have lost count of the number of pet Bash scripts I have encountered in various shops, many of them created by quite talented people. They all had problems. Some typical ones:

    Issue Example
    Most people write bash scripts without dependency checks ‘Of course everyone will have gnu coreutils installed, it’s part of every Linux distro’ - someone runs the script on a Mac
    We need to pass this action out to a command-line tool, that’s obvious Fails if command-line tool isn’t available, no handling errors from tool if they aren’t exactly what’s expected
    Of course people will realise that they need to run this from an environment prepared in this exact (undocumented) way Someone runs the script in a different environment
    Of course people will be running this on x86_64/AMD64, all these third party binaries are available for that Someone runs it on ARM
    Of course people will know what to do if the script fails midway through People try to re-run the script when it fails mid-way through and it’s a mess

    The thing about Ansible is that it can be modular (if you want) and you can use other people’s code but fundamentally it runs one step at a time. You will know for each step:

    • Are dependencies met?
    • Did that step succeed or fail (in realtime!)?
    • (If it failed) what was the error?
    • (Assuming you have written sane Ansible) you can re-run your playbook at any time to get the ‘same’ result. No worries about being left in an indeterminate state
    • (To an extent) It is self-documenting
    • Host architecture doesn’t really matter
    • Target architecture/OS is specified and clear