• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • Proxmox sounds like it fits their use case , it’s a useful and tweakable solution, and because it’s based on KVM you can pass through hardware with IOMMU. Personally, I run Proxmox on my (admittedly not very good) home server with like 12 gigs of ram and a processor from the early 2010s, handles a few VMs just fine with hardware passthrough to a TrueNAS VM. I do run a lot of my micro services on some cheap thin clients (DNS mainly) for redundancy as I mentioned, they were cheap. Home Assistant OS is happy on Proxmox as is Jellyfin with hardware acceleration.







  • floridaman@lemmy.blahaj.zonetoSelfhosted@lemmy.worldShould I move to Docker?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    11 months ago

    Some people seem to hate on it, but I love Docker, it works well for what it has to do and has relatively low overhead as far as I can tell. I personally virtualize a Debian server on Proxmox for my containers just so as to keep everything even more compartmentalized, but it takes more work than it’s worth to set up.

    And if you don’t like Docker for whatever reason, you can also try Podman which is API compatible with Docker for the most part.




  • I self host Bitwarden (Vaultwarden) so I just use the built-in TOTP authenticator in the Bitwarden app. It’s nice to have it all in one place + having auto copy and paste when I log in. And because I self host, it’s all backed up securely and with (as far as I know) no real backdoors.

    ETA: just realized what community this is in. people that replied to me I’m sorry lmao, I’m not a nut about this kinda stuff and I’m by no means recommending this just like using it this way for convenience factor and to keep the likes of google out of my password.







  • I’d recommend an x86 board because as great as the RPI and similar can be, ARM just doesn’t have the same support for a lot of things you might want to self host. I personally like to spring for a used thinclient PC off of eBay, because they have about the same resources as a Raspberry Pi but on an x86 platform. With my thin clients I typically install Alpine but a really light Debian install could work as well, and then from there you can go about installing Docker etc for a little homelab. Even better, if you get lucky and get a couple of them you could mess around with clustering them and some light Kubernetes at home. I’ve got mine running PiHole and Unbound on Alpine to serve my whole house with DNS and it works great. I don’t think I’ve had hardly any downtime issues or anything of that sort.

    TL;DR: try a couple cheap thin clients from eBay and you can run some light stuff on them for cheap.


  • As recommended by others, you might want to use a real public domain that you own, and a reverse proxy for split horizon DNS. I personally run Bind9, Unbound, and PiHole as my DNS servers. Bind9 handles split horizon, so if I request my domain internally it gets routed through Bind. Then bind hands it off to PiHole for adblocking, and PiHole makes requests through Unbound set up as a recursive DNS server which doesn’t rely on any external DNS. I also use Traefik as a reverse proxy for all of my services. My set up is more complicated than necessary, and if you want just a few local domains, PiHole + a reverse proxy is plenty good for your needs.


  • Here is something I wrote previously under a similar post: “Check out the OpenWRT Table of Hardware, it has a list of firmware mod-able off the shelf WiFi routers that work with, you guessed it, OpenWRT. It’s rather versatile as it’s Linux based and can handle VLANs, multiple SSIDs, and of course, you can change the DNS servers.” As I said, OpenWRT is very versatile and runs on many different routers, just find one you like and install it! Many of the supported routers provide Gigabit switching, and some even have multigit for your server connection.