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

help-circle



  • hperrin@lemmy.catoSelfhosted@lemmy.worldHome surveillance set up
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    3 days ago

    I have all Reolink cameras and they’re awesome. They have both indoor and outdoor cameras. They’re really expensive compared to other similar cameras, but the software is really good, and there’s no subscription. You don’t even need to log in. Everything is only stored locally, on either SD cards in the camera or a separate “home hub” (or both). They have motion and object detection built into the cameras.

    The way I have them set up is every indoor camera is plugged into a smart outlet that disconnects their power through Home Assistant when either me or my wife are home.

    The outdoor ones are connected to solar power, so I didn’t even have to run any wires.

    I’d highly recommend them.


  • Safe, yeah. Private, no. If you want to verify whether a user is a real person, you need very personally identifiable information. That’s not ever going to be private.

    The best you could do, in theory, is have a government service that takes that PII and gives the user a signed cryptographic certificate they can use to verify their identity. Most people would either lose their private key or have it stolen, so even that system would have problems.

    The closest to reality you could do right now is use Apple’s FaceID, and that’s anything but private. Pretty safe though. It’s super illegal and quite hard to steal someone’s face.


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