The solutions you’ve mentioned aren’t exactly equivalent. Proxmox is a hypervisor while Docker Swarm and Kubernetes are container orchestration engines. For example, I use Proxmox in a highly available cluster running on three physical nodes. Then I have various VMs and LXC containers running on those nodes. Some of those VMs are Kubernetes nodes running many Docker containers.
I highly recommend Proxmox as it makes it trivial to spin up new containers and VMs when you want to test something out. You can create and destroy VMs in an instant without messing with any of your actual hardware. That’s the power of a good hypervisor.
For orchestration, I would actually recommend you just stick with Docker Compose if you want something very simple to manage. Resiliency or high-availability usually brings with it a lot of overhead (both in system resources as well as maintenance costs) which may not be worth it to you. If you want something simple, Proxmox can run VMs in a highly-available mode so you could have three Proxmox nodes and set any VMs you deem essential to be highly-available within the cluster.
For my set up, I have certain services that are duplicated between multiple Proxmox nodes and then I use failover mechanisms like floating IP addresses to automatically switch things over when a node goes down. I also run most things in Kubernetes which is deployed in a highly-available manner across multiple Proxmox nodes so that I can lose a physical node and still keep (most) of my services running. This however is overkill for most things and I really only do it because I use my homelab to learn and practice different techniques.
TERRAMASTER F2-223 2Bay NAS Storage – High Performance for SMB with N4505 Dual-Core CPU, 4GB DDR4 Memory, 2.5GbE Port x 2, Network Storage Server (Diskless) a.co/d/iT25GwL
I’m kind of excited for LubeLogger, since all the other fuel/maintenance trackers are going down the drain. Currently using Fuelio but I’m not a huge fan.
I’m using terramaster as hdd enclosure. I have two of those, both connected to lenovo thinkcentre. I’ve tried rpi but I needed more power hence the lenovo thingy.
I ripped out the control board of the 2x bay toaster and then bought some sata extension cables (with power) for 2x HDDs. 3D printed a little drive bay type thing and then slapped the raspi on top with the usb controller. It works great!
Works for my usecase of basic NAS /SMB /SFTP and I can stream 1080p etc.
But would look to sata in the future also like you mention, couldn’t find a hat, but USB speeds are fine for me.
I dont know if this qualifies as a “toaster” but Ive used this docking bay in the past for a NAS and it served my purposes decently well. One thing to keep in mind is that random IO will be lacking with a usb interface. Also, this particular chipset does powercycle all the drives when one is removed so drive swaps end up requiring you to power the entire system off to perform. Also no integrated cooling may be a deal breaker as you illuded to.
If I was basing a nas build off of a PI, I would look to use the PCIe 1x2.0 interface on the pi 5 as a HBA.
If the app supports SSO and allows user creation, then it’s just a matter of passing the user claims such as username or email which the app expects from your provider.
I use Authentik as my solution, which uses a GUI for user management and supports all major SSO options, from MFA, to OIDC, SAML, LDAP and more.
Crazy idea, but if you can’t get the bandwidth to support a media server like Jellyfin or Emby where you live, what about placing a server at a trusted relatives or friends house that does have access to high bandwidth? You might need/want to help offset a better internet plan for them though. You could then setup a VPN connection to be able to manage the server remotely and sync files and media to it. You could even use it for off site backup.
selfhosted
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.