• 1 Post
  • 69 Comments
Joined 6 months ago
cake
Cake day: December 13th, 2024

help-circle
  • hperrin@lemmy.catoLinux@lemmy.mlJellyfin assistance
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    7 hours 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!





  • That’s not weird in the sense that it’s unusual, because that’s so usual we have a term for it. And it’s really only weird if you consider it weird. There’s nothing wrong with finding comfort in a familiar object.

    I personally have a Game Boy Color my dad gave to me when I was recovering from surgery when I was 11. I keep it on my TV stand. I was incredibly distraught when I pulled it out of storage and the batteries in it had leaked all over the circuit board, damaging the board beyond repair. My dad actually got me another one on eBay that I harvested the circuit board from to replace mine. I don’t play it, but knowing that it now works and I could play it if I wanted to gives me comfort. I even put the old board in the other Game Boy just so I know that I still have all of the original parts.

    I think it’s probably something most of us do, and I don’t think you should feel any shame in it.


  • Warpinator is meant only to send/receive files and folders, and requires a supported device on both sides.

    QuickDAV lets you send/receive/manage files (meaning you can copy and move files on the host from the client). It doesn’t require a supported device in both sides, since it works with either a WebDAV client or a browser. So as long as one device can run QuickDAV, and the other has at least a browser, it’ll work. (QuickDAV works with a Sega Dreamcast!)

    Warpinator is incredibly easy to use. Open the app on both machines, select the other machine, select the file/folder, send.

    QuickDAV is a bit harder. Open the app on one of the machines, then type the information from the app into the client/browser on the other machine. Then you can download/upload/manage.






  • hperrin@lemmy.catoComic Strips@lemmy.worldImportant Difference
    link
    fedilink
    English
    arrow-up
    44
    arrow-down
    2
    ·
    5 days ago

    Even if it’s not an attack of their argument, and is stated simply as a fact, a personal attack does still work to discredit the opponent to any audience, and can therefore be considered a fallacious ad hominem tactic.

    It’s basically poisoning the well. Even though you’re not explicitly saying it, the audience will infer that someone who can justifiably be described as “shit for brains” should not be trusted on the relevant topic. Even someone profoundly stupid can be right, and even someone incredibly intelligent can be wrong.

    That being said, even if someone has been viciously personally attacked, if the attacker has otherwise proved their argument wrong, that’s what truly matters. It does definitely make me think less of someone if they constantly personally attack their opponent, though.