I am a Meat-Popsicle

  • 0 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • Minimum open services is indeed best practice but be careful about making statements that the attack surface is relegated to open inbound ports.

    Even Enterprise gear gets hit every now and then with a vulnerability that’s able to bypass closed port blocking from the outside. Cisco had some nasty ones where you could DDOS a firewall to the point the rules engine would let things through. It’s rare but things like that do happen.

    You can also have vulnerabilities with clients/services inside your network. Somebody gets someone in your family to click on something or someone slips a mickey inside one of your container updates, all of a sudden you have a rat on the inside. Hell even baby monitors are a liability these days.

    I wish all the home hardware was better at zero trust. Keeping crap in isolation networks and setting up firewalls between your garden and your clients can either be prudent or overkill depending on your situation. Personally I think it’s best for stuff that touches the web to only be allowed a minimum amount of network access to internal devices. Keep that Plex server isolated from your document store if you can.




  • I’d vote for anytype or obsidian

    Anytype has a learning curve, But it has built-in encryption and IPFS syncing provided by the company. The templating system is really slick and the relational aspect is pretty solid.

    Obsidian + syncthing fork is a really solid contender. It’s much easier to work with out of the box but the features are a little more generic.

    Neither of these are really self-hosted, so much as they are contained in their own ecosystem. You get some measure of higher availability that you have to really work for if you’re really self-hosting a product.














  • I’m running something surprisingly close to most of what you’re asking for sans the immich which I’m waiting on stability from them first. That warning at the time of their site that says it’s under constant development and not to use it as your primary picture store is a bit worrisome.

    Unraid with 2 video cards

    • Plex Container (primary video card)
    • Plex VM (pass through secondary card handles DVR and backups and it’s also my steam remote provider)
    • Home assistant VM (running it in a VM is nicer than a container because of HAOS)
    • Jellyfin container
    • All the video services pull from the same catalog. I use jellyfin frequently but secondarily, it is my backup in case Plex heads in a direction I don’t like. They’ve already shown some indications I’m not going to like them in the future.
    • Deluge+VPN container
    • Cloudflare container (first set up is actually a pain in the ass)
    • Tailscale plugin
    • SearxNG container self-hosted search engine tool
    • Pi hole in a container
    • Pi hole on a raspberry pi

    Plex gets accessed remotely via its own remote capabilities

    Jellyfin gets accessed remotely via tailscale

    SearXNG is access remotely via cloudflare

    I have a secondary Plex server sitting on a raspberry pi with the backup pi hole

    I am preparing to set up a peertube. Haven’t had a lot of luck with the container on unraid. I run a fair amount of proxmox at work so I’ll probably just use proxmox for it.

    I run a separate dedicated system completely for my cameras. Not running frigate yet but I’ll get around to it eventually using blue iris at the moment.

    My unraid gets as much uptime as updates allow. I love being able to just jbod my media discs together and still have some protection with parity.

    I find the containerized version of Plex to be more stable than my VM version but that’s probably my own fault as I’m oversubscribing the vm.