• 1 Post
  • 50 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle
  • 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





  • GitLab just doesn’t compare in my view:

    To begin with, you have three different major versions to work with:

    • Self-Hosted open source
    • SAAS open source
    • Enterprise SAAS

    Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what’s documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

    Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I’m speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

    I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I’d never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you’re expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn’t or at least wasn’t 6 months ago.






  • I’m sorry to say but it’s Windows. You never really know. Have you considered getting an old optiplex on Amazon Renewed and putting Debian and Jellyfin on that?

    Update for the people downvoting:

    I am a professional platform engineer. By ‘Windows. You never really know’ I mean that there are always ten thousand things running, you’re never going to have a full grasp of everything that’s happening in the way that you could with a stripped down linux environment. My own Jellyfin instance is running on

    • Intel® Core™ i5-4590S CPU @ 3.00GHz
    • 8GB RAM
    • Integrated Graphics
    • Shipped AUG 2014
    • Ubuntu 22.04 with deb installation of Jellyfin

    All clients connect via Wifi although server is cat5 to switch. Most of my video does not require transcoding. There are plenty of FLAC audio files in my library. I don’t see slowdowns as described here.










  • Very lightweight article. Let’s consider a different marketing angle:

    Scene: Deutsche Telekom boardroom

    CEO: we want a way to differentiate our devices

    CTO: you mean like back in the 00’s when we built our crapplets into the firmware for feature phones using our network, made them non uninstallable and permanent default for common operations?

    CEO: yes, exactly! We used to have a Deutsche Telekom web browser, a DT messaging app, DT social media app…

    CTO: Customers today wouldn’t go for that. They want iPhones and Google play store. Look what happened with Huawei.

    CEO: we just need to convince them that they don’t need any of that… And make sure that they couldn’t install third party stuff after market…

    CTO: so a phone with no apps then?

    CEO: no, a phone with one app that can do everything, that we control.

    CTO: how are we going to sell a phone with a single pre installed app and convince customers that it’s better than having an app store? How can we convince them it can do everything?

    CEO and CTO together: We call it AI interface!