• 7 Posts
  • 1.04K Comments
Joined 6 months ago
cake
Cake day: December 13th, 2024

help-circle













  • That’s a very good example of confirmation bias. I’m not saying that those workers weren’t a problem, but I am definitely saying you pointing out that they were “DEI hires” is confirmation of existing biases.

    If you hired bad workers, that’s the company’s fault. DEI doesn’t mean “hire any minority person”. DEI means don’t skip hiring someone because they’re a minority. It means when you find a qualified candidate, you should hire them, even if they’re black or a woman, for example. I’m sorry that your company seemed to misunderstand this. It’s a pretty common misconception, because conservatives want people to believe that DEI initiatives are something that they’re not. They want white men to believe that DEI initiatives are “taking away their jobs”.

    And just because someone is a white straight cis man doesn’t mean they’ll be a good worker. The majority of shitty workers I’ve seen were white straight cis men. That’s probably because the majority of workers I’ve seen were white straight cis men, and that’s how statistics works.


  • If someone is really sick of everyone calling them a racist, maybe the problem is actually them being a racist. I can count on one hand the number of times I’ve been called a racist in my nearly four decades of life, and every time it was by a conservative claiming I was being racist against white people. (I am a white man.) I am extremely opinionated and very open about my opinions. So the problem seems not to be that everyone with a loud opinion is labeled a racist.

    And yes, you were literally talking about racists not feeling able to express their opinions without consequences. I don’t view that as a problem. There should be consequences for expressing a racist opinion.

    It is rather telling though that nowhere in my comment did I claim that you are racist, but that’s how you interpreted it.





  • hperrin@lemmy.catoLinux@lemmy.mlJellyfin assistance
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    5 days ago

    So, Jellyfin is one of those apps where the Docker documentation is really lacking. I’m gonna give you my docker-compose.yml file in case it helps:

    services:
      jellyfin:
        image: jellyfin/jellyfin
        user: 0:0
        restart: 'unless-stopped'
        ports:
          - '8096:8096'
        environment:
          #- JELLYFIN_CACHE_DIR=/var/cache/jellyfin
          #- JELLYFIN_CONFIG_DIR=/etc/jellyfin
          - JELLYFIN_DATA_DIR=/var/lib/jellyfin
          - JELLYFIN_LOG_DIR=/var/log/jellyfin
        volumes:
          - ./config:/config
          - ./cache:/cache
          - ./data:/var/lib/jellyfin
          - ./log:/var/log/jellyfin
          - /data/jellyfin:/data/jellyfin
        devices:
          - /dev/dri
    

    For me /data/ is my RAID array, which is why my jellyfin data directory is there. Everything else goes in the same directory as the compose file. My system has a graphics card that does transcoding (Arc A380), so I have /dev/dri under devices.

    You should learn a lot about Docker Compose, because it will help you tremendously. I use Jellyfin behind an Nginx Proxy Manager reverse proxy. I’d highly recommend it. Here’s my compose file for that:

    services:
      app:
        image: 'jc21/nginx-proxy-manager:latest'
        restart: unless-stopped
        network_mode: "host"
        #ports:
        #  - '80:80'
        #  - '81:81'
        #  - '443:443'
        volumes:
          - ./data:/data
          - ./letsencrypt:/etc/letsencrypt
    

    Running in “host” mode is important, instead of just forwarding ports, because it lets you forward things to localhost, like pointing https://media/.[mydomain]/ to http://127.0.0.1:8096/ for Jellyfin.

    Anyway, best of luck to you, and I hope that helps!