I have something like this, in the same case. I have beefier specs b/c I use it as a daily workstation in addition to running all my stuff. * nginx with letsencrypt wildcard so I have lots of subdomains * No tailscale, just pure wireguard between a few family houses and for remote access * Jellyfin for movies and TV, serving to my Samsung TV via the Tizen jellyfin app * Mopidy holding my music collection, serving to…
For anyone considering this, it's not a good plan to do it this way, if you have any family members relying on these services, you have to kill them all every time you reboot your workstation. It's really not great to mix destop and server like this. (speaking from experiance and I really need to get a separate box setup for this self hosted stuff)
My Homelab Setup
211–220 of 232 posts
Re: My Homelab Setup
#212Earlier quoted context omitted.
> You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep". Huh, why? I have a homelab, I don't have any downtime except when I need to restart services after changing something, or upgrading stuff, but that happens what, once every month in total, maybe once every 6 months or so per ser…
> I don't have any downtime except when I need to restart services So... you have downtime then. (Also, you should be rebooting regularly to get kernel security fixes). > not sure why you'd need Kubernetes at all here To get HA, which is what we are talking about. > only serves to complicate Yes, high-availability systems are complex. This is why I am saying it's not really feasible for a homelabber, unless we are k8…
5 seconds of downtime as you change from port N to port N+1 is hardly "downtime" in the traditional sense.
> To get HA, which is what we are talking about.
Again, not related to Kubernetes at all, you can do it easier with shellscripts, and HA !== orchestration layer.
Re: My Homelab Setup
#213Earlier quoted context omitted.
> Why do you need to dilute the term? Nobody is diluting anything. This person posted the setup they have in their home. It’s their homelab. It’s not diluting any terms for them to call it that. Their setup is just as much a homelab as somebody else’s 48U rack. It’s just a dick move, and against the rules of the site, to see somebody’s earnest post about their tech setup and post a shallow dismissal about how their s…
They are not researching anything. They just want to have few things running. The whole idea of homelab (regardless of size) is learning first. He just have home server. It's okay to call it that
Re: My Homelab Setup
#214Earlier quoted context omitted.
In the 1Password entry go to the "website" item. To right right there's an "autofill behavior" button. Change it to "Only fill on this exact host" and it will no longer show up unless the full host matches exactly
Is this a per-item behaviour or can this be set as a global default? I'm guessing this is 1Password 8 only, as I can't see this option in 1Password 7.
Re: My Homelab Setup
#215Earlier quoted context omitted.
For anyone considering this, it's not a good plan to do it this way, if you have any family members relying on these services, you have to kill them all every time you reboot your workstation. It's really not great to mix destop and server like this. (speaking from experiance and I really need to get a separate box setup for this self hosted stuff)
It's also worth noting you don't need sophisticated hardware to run anything listed in the parent comment. 8GB of RAM and a Celeron would be adequate. More RAM might be nice if you use the NAS a lot.
Re: My Homelab Setup
#216Earlier quoted context omitted.
You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep". (Probably a lot of the services I run don't even really support HA properly in a k8s system with replicas. E.g. taking global exclusive DB locks for the lifetime of their process)
> You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep". Huh, why? I have a homelab, I don't have any downtime except when I need to restart services after changing something, or upgrading stuff, but that happens what, once every month in total, maybe once every 6 months or so per ser…
Re: My Homelab Setup
#217Earlier quoted context omitted.
> I don't have any downtime except when I need to restart services So... you have downtime then. (Also, you should be rebooting regularly to get kernel security fixes). > not sure why you'd need Kubernetes at all here To get HA, which is what we are talking about. > only serves to complicate Yes, high-availability systems are complex. This is why I am saying it's not really feasible for a homelabber, unless we are k8…
> So... you have downtime then. 5 seconds of downtime as you change from port N to port N+1 is hardly "downtime" in the traditional sense. > To get HA, which is what we are talking about. Again, not related to Kubernetes at all, you can do it easier with shellscripts, and HA !== orchestration layer.
Re: My Homelab Setup
#218Re: My Homelab Setup
#219I'll admit I've still stuck with the original FreeBSD based TrueNAS, and still am kinda bummed they swapped it. So it's interesting to see a direct example of someone for whom the new Linux based version is clearly superior. I'm long since far, far more at the "self-hosted" vs "homelab" end of the spectrum at this point, and in turn have ended up splitting my roles back out again more vs all-in-one boxes. My NAS is j…
One of the most helpful realizations I had as I played around with self-hosting at home is that there is nothing magical about a NAS. You don't need special NAS software. You generally don't need wild filesystems, or containers or VMs or this-manager or that-webui. Most people just need Linux and NFS. Or Linux and SMB. And that's kind of it. The more layers running, the more that can fail. Just like you don't really…
Re: My Homelab Setup
#220Earlier quoted context omitted.
One of the most helpful realizations I had as I played around with self-hosting at home is that there is nothing magical about a NAS. You don't need special NAS software. You generally don't need wild filesystems, or containers or VMs or this-manager or that-webui. Most people just need Linux and NFS. Or Linux and SMB. And that's kind of it. The more layers running, the more that can fail. Just like you don't really…
Same with a router. Any Linux box with a couple of (decent) NICs is a powerful router. You just need to configure it. But for my own sanity I prefer out of the box solutions for things like my router and NAS. Learning is great but sometimes you really just need something to work right now!