• 0 Posts
  • 75 Comments
Joined 1 year ago
Cake day: June 26th, 2023
  • tux7350@lemmy.worldtoLinux@lemmy.world•Sharing Plex data between seperate installations?English
    3·
    20 days ago

    Running Plex in a docker container will be your best bet. After installing docker you can run a docker compose file that has your /config folder mapped to a separate location. Here is a sample compose file from the linuxserver.io group, which I highly recommend.

    ---
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - VERSION=docker
      - PLEX_CLAIM= #optional
    volumes:
      - /path/to/plex/library:/config
      - /path/to/tvseries:/tv
      - /path/to/movies:/movies
    restart: unless-stopped

    Pay special attention to the section marked “volumes” you’ll see the first line is a mapping for the plex config from the host to inside the container. The left side of the “:” is the path as the host sees it, the right side is from inside the container. You can use this compose file in each installation of linux to share your config and watch history as plex will always find it in the /config folder. That’s the beauty of containerization!

    That being said I wouldn’t run two containers at the same time. That could have unintended consequences as each may try to write to the same file at the same time. As long as only one instance of plex is using the config at a time you’ll be alright. You can find more info about the compose file here!

    If you have any questions, feel free to ask! 😁

  • tux7350@lemmy.worldtoProgrammer Humor@programming.dev•Still relevant, just substitute for win 11
    1·
    1 month ago

    It’s really not that hard to use a local account. When it askes for a Microsoft account just hit SHIFT+F10 then type in the command “oobe\bypassnro” and the pc will reboot. Now just don’t let the computer connect to internet, and when it askes for internet hit “I don’t have an internet connection” and then it will let you continue with a local account.

    …I admit though… as I typed that out its pretty annoying lol Not hard, but like… just annoying.

  • tux7350@lemmy.worldtoSelf-hosting@slrpnk.net•Help wanted: best Home server, Nextcloud, Atomic setup with DynDNS?
    2·
    1 month ago

    I’m going to suggest something a bit more out there. You can setup this whole thing with NixOS. I have a bunch of docker containers that run as a systemd service, declared with Nix and personally, I like it very much. It’s also got everything else you want but the atomic upgrades are top tier in NixOS.

    For example if you want NoIP and Cockpit just add this bit to your configuration.nix

        environment.SystemPackages =[
        pkgs.noip
        pkgs.cockpit
    ];

    Adding something like docker or podman is just as easy with a one line like

        virtualisation.docker.enable = true;

    There is always a bit of a learning curve when doing anything with Nix but I find the buy in to be worth it. Here’s a blog post about converting docker compose files over to the Nix format. This really isnt necessary as you could just make the systemd service run a oneshot against a docker compose file but this blog has a lot of nice examples.

    https://mrupnikm.github.io/en/posts/nix-docker-containers/

    If you have any questions please let me know :D

  • tux7350@lemmy.worldtoSelfhosted@lemmy.world•What's the easiest way to host a music colletion (FLAC)?English
    3·
    2 months ago

    It shouldn’t mess with your current routing but if you’re running other VPNs you may run into issues.

    After you join the machines to the tailnet, each machine gets a new IP address ( only visible to other machines in the tailnet), by default it’s a 100.x.y.z you can check the tailnet for the device IP.

    Now you can keep the port closed on your router and it will still be accessible over the usual lan ip and port. But when you want to access remotely, turn on tailscale and connect using the tailnet IP.

    Another cool thing you can do with this setup is turn your home server into an exit node. By default it will only route things that are in the tailnet (100.x.y.z subnet). But if you turn your home server into an exit node you can funnel all your traffic back through the exit node. Instant free VPN back home!