• 0 Posts
  • 45 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.









  • SquiffSquiff@lemmy.worldtoTechnology@lemmy.worldThe Mac vs. PC war is back on?
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    2
    ·
    4 months ago

    If you look at the price for a Mac versus a Windows computer, I think it’s pretty obvious why people might choose a Windows device. For Linux, you really have to know where to look to buy a laptop that is shipped or warrantied with Linux. People tend to buy Windows computers because that’s what’s advertised available, familiar and in their price bracket.

    Disclaimer: my main laptop is Mac. I have a secondary one running Linux and although I have a work laptop running Windows, that wasn’t my choice and I don’t have Windows on any personal devices.