It really bugs me in general how often the term “home lab” is conflated with a “home server”, but in the context of what this article is trying to communicate, it’s only going to turn the more casually technical people it’s trying to appeal to off.
For many people, their home lab can also function as a server for self hosting things that aren’t meant to be permanent, but that’s not what a home lab is or is for. A home lab is a collection of hardware for experimenting and prototyping different processes and technologies. It’s not meant to be a permanent home for services and data. If the server in your house can’t be shut down and wiped at any given time without any disruption to or loss of data that’s important to you, then you don’t have a home lab.
Only if nothing on it is permanent. You can have a home lab where the things you’re testing are self hosted apps. But if the server in question is meant to be permanent, like if you’re backing up the data on it, or you’ve got it on a UPS you make sure it stays available, or you would be upset if somebody came by and accidentally unplugged it during the day, it’s not a home lab.
A home lab is an unimportant, transient environment meant for tinkering, prototyping, and breaking.
A box that’s a solution to something, that’s hosting anything you can’t get rid of at a moments notice, is just a home server.
I still use the label ‘homelab’ for everything in my house, including the production services. It’s just a convenient term and not something I’ve seen anyone split hairs about until now.
if nothing on it is permanent. You can have a home lab where the things you’re testing are self hosted apps. But if the server in question is meant to be permanent, like if you’re backing up the data on it, or you’ve got it on a UPS you make sure it stays available, or you would be upset if somebody came by and accidentally unplugged it during the day, it’s not a home lab.
A home lab is an unimportant, transient environment me
Based on what I’ve seen, I’d also say a homelab is often needlessly complex compared to what I’d consider a sane approach to self hosting. You’ll throw all sorts of complexity to imitate the complexity of things you are asked to do professionally, that are either actually bad, but have hype/marketing, or may bring value, but only at scales beyond a household’s hosting needs and far simpler setups will suffice that are nearly 0 touch day to day.
Oh yeah like that’s part of it. If this article is supposed to be a call to action, somebody who starts looking into “homelabs” is going to get confused, they’ll get some sticker shock, and they won’t understand how they apply to what’s said in the article. They’ll see a mix of information from small home servers to hyperconverged infrastructure, banks of Cisco routers and switches, etc. my first home lab was a stack of old Cisco gear I used to study for my network engineering degree. If you stumbled upon an old post of mine talking about my setup and all you’re looking for is a Plex box you’ll be like “What the fuck is all this shit, I’m not trying to deal with all that”
“Self hosting”, and “home server” are just more accurate keywords to look into and actually see things more closely related to what you want.
Yep, and I see evidence of that over complication in some ‘getting started’ questions where people are asking about really convoluted design points and then people reinforcing that by doubling down or sometimes mentioning other weird exotic stuff, when they might be served by a checkbox in a ‘dumbed down’ self-hosting distribution on a single server, or maybe installing a package and just having it run, or maybe having to run a podman or docker command for some. But if they are struggling with complicated networking and scaling across a set of systems, then they are going way beyond what makes sense for a self host scenario.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
It really bugs me in general how often the term “home lab” is conflated with a “home server”, but in the context of what this article is trying to communicate, it’s only going to turn the more casually technical people it’s trying to appeal to off.
For many people, their home lab can also function as a server for self hosting things that aren’t meant to be permanent, but that’s not what a home lab is or is for. A home lab is a collection of hardware for experimenting and prototyping different processes and technologies. It’s not meant to be a permanent home for services and data. If the server in your house can’t be shut down and wiped at any given time without any disruption to or loss of data that’s important to you, then you don’t have a home lab.
removed by mod
Only if nothing on it is permanent. You can have a home lab where the things you’re testing are self hosted apps. But if the server in question is meant to be permanent, like if you’re backing up the data on it, or you’ve got it on a UPS you make sure it stays available, or you would be upset if somebody came by and accidentally unplugged it during the day, it’s not a home lab.
A home lab is an unimportant, transient environment meant for tinkering, prototyping, and breaking.
A box that’s a solution to something, that’s hosting anything you can’t get rid of at a moments notice, is just a home server.
removed by mod
removed by mod
removed by mod
removed by mod
removed by mod
removed by mod
I still use the label ‘homelab’ for everything in my house, including the production services. It’s just a convenient term and not something I’ve seen anyone split hairs about until now.
Based on what I’ve seen, I’d also say a homelab is often needlessly complex compared to what I’d consider a sane approach to self hosting. You’ll throw all sorts of complexity to imitate the complexity of things you are asked to do professionally, that are either actually bad, but have hype/marketing, or may bring value, but only at scales beyond a household’s hosting needs and far simpler setups will suffice that are nearly 0 touch day to day.
Oh yeah like that’s part of it. If this article is supposed to be a call to action, somebody who starts looking into “homelabs” is going to get confused, they’ll get some sticker shock, and they won’t understand how they apply to what’s said in the article. They’ll see a mix of information from small home servers to hyperconverged infrastructure, banks of Cisco routers and switches, etc. my first home lab was a stack of old Cisco gear I used to study for my network engineering degree. If you stumbled upon an old post of mine talking about my setup and all you’re looking for is a Plex box you’ll be like “What the fuck is all this shit, I’m not trying to deal with all that”
“Self hosting”, and “home server” are just more accurate keywords to look into and actually see things more closely related to what you want.
Yep, and I see evidence of that over complication in some ‘getting started’ questions where people are asking about really convoluted design points and then people reinforcing that by doubling down or sometimes mentioning other weird exotic stuff, when they might be served by a checkbox in a ‘dumbed down’ self-hosting distribution on a single server, or maybe installing a package and just having it run, or maybe having to run a podman or docker command for some. But if they are struggling with complicated networking and scaling across a set of systems, then they are going way beyond what makes sense for a self host scenario.