Hard agree. In fact, I think there’s a market for JUST the guides. It’s true that there’s a TON of guides out there already, from old blogs to YouTube, but the issue is: all of them start or end with: “your use case might differ, so perhaps this solution isn’t for you.” Or “make sure this setup is compatible with your specific hardware”
For example: I want to set up some sort of backup/cloud storage type system. Well there’s about 1400 ways to accomplish that. I can easily just grab one and go, but I’ll always wonder- should I have done this a different way? Would my life be easier/more secure if I chose a different set up?
So offering hardware that is compatible with whatever “stack” of services included would be a huge plus. Sorta like getting a raspberry pi and following a specific raspberry pi tutorial- you know the issues you get aren’t gonna be due to incompatibility.
I think it really boils down to the scale of one’s home lab- are you just tinkering to get some skills and make something cool? Or are you hoping to do something much much bigger? Different software solutions fit those extremes differently.
Sorry, got off rambling there. I guess I’ve been down the home lab hardware/software wormhole for too long these last few weeks.
EliRibble@lemmy.world 2 months ago
Interesting, so if you got hardware and it came with guides, what kind of guides would you want? I would assume something layered. At the top is just “I want to install these 5 apps and use them, I don’t care how it works” and in the middle is “I’m ready to SSH into the router and create some VLANs for fun” at the bottom is something like “I want to flash my own firmware with appropriate certificates for secure boot and my own root chain of trust on the server hardware”.
_bcron@lemmy.world 2 months ago
The guides, basically a quick and dirty walkthrough on setting it up, hopefully a few explanations about things, and a handful of common troubleshooting tips. Also pointers to a handful of communities that have helpful info in case something obscure pops up.
Basically, teach a man how to fish, as opposed to giving him a couple.
I think a lot of people who would otherwise dabble with a DIY home server never try because it’s pretty technical (beyond typical ‘build a pc’ stuff) so I think the education that would come with the hardware would be appreciated by many. Help them get their foot in the door by making the dive a little less scary
acockworkorange@mander.xyz 2 months ago
I could see this being a use case for a NixOS deployment where your company manages the configuration file and versioning of the system, as well as providing support. Over time, I’d you’re diligent about building documentation based off of each support request, you’ll end up with a personalized guide. And if your customer decides take a break or quit entirely, they have a configured system that doesn’t lock them in into something too esoteric.
Disclaimer: I only know of Nix, never used it because I just don’t manage that many machines to be worth my while to learn it.