[deleted]
My Homelab Setup
31–40 of 232 posts
Re: My Homelab Setup
#32I'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…
> splitting my roles back out again more The fiasco you can cause when you try fix, update, change etc makes this my favourite too. Household life is generally in some form of ‘relax’ mode in evening and at weekends. Having no internet or movies or whatever is poorly tolerated. I wish Apple was even slightly supportive of servers and Linux as the mini is such a wicked little box. I went to it to save power. Just chec…
>The fiasco you can cause when you try fix, update, change etc makes this my favourite too.
I think some of the difference between "self-hosted" vs "homelab" is in the answer to the question of "What happens if this breaks end of the day Friday?" An answer of "oh merde of le fan, immediate evening/weekend plans are now hosed" is on the self-hosted end of the spectrum, whereas "eh, I'll poke at it on Sunday when it's supposed to be raining or sometime next week, maybe" is on the other end. Does that make sense? There are a few pretty different ways to approach making your setup reliable/redundant but I think throwing more metal at the problem features in all of them one way or another. Plus if someone moves up the stack it can simply be a lot more efficient and performant, the sort of hardware suited for one role isn't necessarily as well suited for another and trying to cram too much into one box may result in someone worse AND more expensive then breaking out a few roles.
But probably a lot of people who ended up doing more hosting started pretty simple, dipping their toes in the water, seeing how it worked out and building confidence. And having everything virtualized on a single box is a pretty easy and highly flexible way get going and experiment. Also if it's on a ZFS backing makes "reset/rollback world" quite straight forward with minimal understanding given you can just use the same snapshot mechanism for that as you do for all other data. Issues with circular dependencies and the like or what happens if things go down when it's not convenient for you to be around in person don't really matter that much. I think anything that lowers the barrier to entry is good.
Of course, someone can have some of each too! Or be somewhere along the spectrum, not at one end or another.
Re: My Homelab Setup
#33>Because all of my services share the same IP address, my password manager has trouble distinguishing which login to use for each one. In Bitwarden they allow you to configure the matching algorithm, and switching from the default to "starts with" is what I do when I find that it is matching the wrong entries. So for this case just make sure that the URL for the service includes the port number and switch all items t…
I wonder why each service doesn’t have a different subdomain.
Re: My Homelab Setup
#34Neat! > Right now, accessing my apps requires typing in the IP address of my machine (or Tailscale address) together with the app’s port number. You might try running Nginx as an application, and configure it as a reverse proxy to the other apps. In your router config you can setup foo.home and bar.home to point to the Nginx IP address. And then the Nginx config tells it to redirect foo.home to IP:8080 and bar.home t…
Personally I'm using haproxy for this purpose, with Lego to generate wildcard SSL certs using DNS validation on a public domain, then running coredns configured in the tailnet DNS resolvers to serve A records for internal names on a subdomain of the public one.
I've found this to work quite well, and the SSL whilst somewhat meaningless from a security pov since the traffic was already encrypted by wire guard, makes the web browser happy so still worthwhile.
Re: My Homelab Setup
#35Neat! > Right now, accessing my apps requires typing in the IP address of my machine (or Tailscale address) together with the app’s port number. You might try running Nginx as an application, and configure it as a reverse proxy to the other apps. In your router config you can setup foo.home and bar.home to point to the Nginx IP address. And then the Nginx config tells it to redirect foo.home to IP:8080 and bar.home t…
Or just use Tailscale serve to put the app on a subdomain
Re: My Homelab Setup
#36This is extremely light - not a bad setup, but I mean.. it's like 1% of typical Homelabs.
Of typical homelabs that are posted and discussed.
The online activity of the homelab community leans towards those who treat it as an enjoyable hobby as opposed to a pragmatic solution.
I'm on the other side of the spectrum. Devops is (at best) a neutral activity; I personally do it because I strongly dislike companies being able to do a rug-pull. I don't think you'll see setups like mine too often, as there isn't anything to brag about or to show off.
Re: My Homelab Setup
#37Earlier quoted context omitted.
Why do we need to gatekeep “homelab”?
Terms making defined sense aid in conversation. Why do you need to dilute the term? There is nothing wrong with your NAS running 3 apps that you press update once a year not being called "homelab" but just "a NAS"
I think if you’re playing around with apps & Tailscale on your NAS, it’s a homelab.
Re: My Homelab Setup
#38Earlier quoted context omitted.
Why do we need to gatekeep “homelab”?
Terms making defined sense aid in conversation. Why do you need to dilute the term? There is nothing wrong with your NAS running 3 apps that you press update once a year not being called "homelab" but just "a NAS"
> 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 setup isn’t deserving of your imagined barrier to entry.
Re: My Homelab Setup
#39Have a look at Headscale to avoid the cost of Tailscale for small home setups.
Re: My Homelab Setup
#40>Because all of my services share the same IP address, my password manager has trouble distinguishing which login to use for each one. In Bitwarden they allow you to configure the matching algorithm, and switching from the default to "starts with" is what I do when I find that it is matching the wrong entries. So for this case just make sure that the URL for the service includes the port number and switch all items t…
This is always annoying me with 1Password, before that I just always added subdomains but now I'm usually hosting everything behind Tailscale which makes this problem even worse as the differentiation is only the port.
You can still have subdomains with Tailscale. Point them at the tailscale IP address and run a reverse proxy in front of your services