Main Page: Difference between revisions
Lynn Macey (talk | contribs) No edit summary |
Lynn Macey (talk | contribs) No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
=Introduction= | |||
This wiki covers my journey toward the perfect Homelab/Home server for me. This likely is not the perfect one for you. | |||
I am a retired IP professional who spent 45 years in the trenches doing much this same work and got paid for it. Now I do it for fun and, face it, it keeps off of the streets and out of jail. | |||
[[How did I get here?]] | |||
I have been through a lot of hardware, software and solutions over the years. As of now, I am regretting scrapping some of the hardware that arrived over time. I don't feel bad about getting rid of the large 1U and 2U servers that I had at one time. They were not terribly fast, but very noisy and power hungry. After my wife and I downsized from a medium sized house to a 2 BR apartment, it made no sense to keep them. Yes, they were fun to tinker with, but they were also a sledgehammer to the fine task that I was attempting to accomplish. | |||
[[The Network and Home Servers]] | |||
I have been through a number of solution packages getting to where I am, and I am largely still looking. Hopefully I will be able to declare success in the relatively near future... | |||
Like many of you I started out with discrete tools as I was learning how to use Docker. I am not sure how I would get along without this tool. Below I will list what I feel are the strengths and weaknesses of the configurations that I have tried. To a large degree, if you starting out building a home lab, you need to have the ability to manage the configuration that you pt together because generally none of them are a perfect solution. One of the common problems since the developers are likely to be home hobbyists like ourselves, The projects tend to stall out after a while. The developer moves on or experiences people being demanding, ungrateful and sometimes just plain nasty. | |||
I have been willing, and happy, to pay them subscription fees to fund their efforts. These are usually modest, typically equivalent to two or three lattes a month. Getting traction on their part is often difficult and reaching critical mass generally doesn't happen. I recognize that most of these people have real jobs and developing the code is just a side gig that helps to pay the electric bill and buy some hardware. So, with that, let me tell you how I got to here. | |||
[[The Homelab Stack History]] | |||
The stack implementation progression has been SimpleHomeLab, Funky Penguin, YAMS and then Deployrr. I am now working with The TrueNAS-Compose suite. I have tried to give a reasoned top-level assessment of the good and bad aspects of the tool on the assessment page. | |||
[[The assessments are here]] | |||
For more of a deep dive deep dive into them just head over here: | |||
[[Technical details are here]] | |||
Latest revision as of 18:43, 20 August 2026
Introduction
This wiki covers my journey toward the perfect Homelab/Home server for me. This likely is not the perfect one for you.
I am a retired IP professional who spent 45 years in the trenches doing much this same work and got paid for it. Now I do it for fun and, face it, it keeps off of the streets and out of jail.
I have been through a lot of hardware, software and solutions over the years. As of now, I am regretting scrapping some of the hardware that arrived over time. I don't feel bad about getting rid of the large 1U and 2U servers that I had at one time. They were not terribly fast, but very noisy and power hungry. After my wife and I downsized from a medium sized house to a 2 BR apartment, it made no sense to keep them. Yes, they were fun to tinker with, but they were also a sledgehammer to the fine task that I was attempting to accomplish.
I have been through a number of solution packages getting to where I am, and I am largely still looking. Hopefully I will be able to declare success in the relatively near future...
Like many of you I started out with discrete tools as I was learning how to use Docker. I am not sure how I would get along without this tool. Below I will list what I feel are the strengths and weaknesses of the configurations that I have tried. To a large degree, if you starting out building a home lab, you need to have the ability to manage the configuration that you pt together because generally none of them are a perfect solution. One of the common problems since the developers are likely to be home hobbyists like ourselves, The projects tend to stall out after a while. The developer moves on or experiences people being demanding, ungrateful and sometimes just plain nasty.
I have been willing, and happy, to pay them subscription fees to fund their efforts. These are usually modest, typically equivalent to two or three lattes a month. Getting traction on their part is often difficult and reaching critical mass generally doesn't happen. I recognize that most of these people have real jobs and developing the code is just a side gig that helps to pay the electric bill and buy some hardware. So, with that, let me tell you how I got to here.
The stack implementation progression has been SimpleHomeLab, Funky Penguin, YAMS and then Deployrr. I am now working with The TrueNAS-Compose suite. I have tried to give a reasoned top-level assessment of the good and bad aspects of the tool on the assessment page.
For more of a deep dive deep dive into them just head over here:
Consult the User's Guide for information on using the wiki software.
