←back to thread

Show HN: I built a(nother) house optimized for LAN parties

(lanparty.house)
1071 points kentonv | 2 comments | 16 Nov 24 15:52 UTC | HN request time: 0s | source

I wasn't quite sure if this qualified as "Show HN" given you can't really download it and try it out. However, dang said[0]:

> If it's hardware or something that's not so easy to try out over the internet, find a different way to show how it actually works—a video, for example, or a detailed post with photos.

Hopefully I did that?

Additionally, I've put code and a detailed guide for the netboot computer management setup on GitHub:

https://github.com/kentonv/lanparty

Anyway, if this shouldn't have been Show HN, I apologize!

[0] https://news.ycombinator.com/item?id=22336638

Show context
9x39 ◴[17 Nov 24 01:19 UTC] No.42161153[source]▶
Given it's only 20 pcs, I might have just opted for fully local machines with a basic disk overlay software with exceptions for where Steam and Epic live. Course, engineering a centralized solution can be fun, but locked-down PCs are just simple. Having built corporate RDP and VDI solutions I'm just biased towards keeping things simple these days and pushing admin work off myself.

Going off the local PC only idea, you could script just your rebuilds of them in the off chance something goes south, along with maybe a disk image with the majority of common games loaded. This is just thinking along the lines it's friends and family, not the general public. I'd probably use gigabit Internet (or more) which makes updates you're missing fast, while Steam lets PCs on a LAN share updated files and save bandwidth.

Did you consider patch panels or things like PatchBox to organize those UTP cables or allow for changes in your switching later?

replies(1): >>42161299 #
kentonv ◴[17 Nov 24 01:47 UTC] No.42161299[source]▶
Hmm, that sounds like a lot more maintenance work to me.

The way I have it set up, I am essentially maintaining only one PC, in a totally normal way. I update Windows by pulling up Windows Update in the control panel, etc. Since I only have to do it for one machine this is fine -- orchestrating updating 20 machines sounds like a pain. Yeah I know there are enterprise tools for this but why bother?

Once I've updated that one machine I just run one command on the server and now all the machines have cloned it. At the end of the party I run one command and all the machines are reverted.

Also I can give everyone full admin access to their machine (which you sometimes need for games) and not have to worry about it, because I know it'll all be completely reverted later.

replies(2): >>42161619 #>>42162180 #
1. 9x39 ◴[17 Nov 24 05:25 UTC] No.42162180[source]▶
Ah, I think I see where I failed to explain what I meant.

You could skip the orchestration and remote storage layers altogether and cut your commands you run down to ~0 with local nvme SSDs. What orchestration do PCs running Steam and Epic need? Machines can just auto-update, unless you really like reinventing that or only have a few megabits of bandwidth.

Again, it's not that the netboot setup isn't cool to see built, I was just thinking out loud how to simplify it even further.

replies(1): >>42162222 #
2. kentonv ◴[17 Nov 24 05:37 UTC] No.42162222[source]▶
I guess you're suggesting I leave the machines on and hope they all update themselves in the background.

I don't think that would really work. Not all the changes I make to machines before a party are things that they'd do automatically if just left to sit. E.g. I usually install some new games some people suggested, or download the latest nvidia driver directly from the web site (where they are available before Windows Update gets them), or remove games we aren't playing anymore to free up space (or because they are constantly downloading enormous updates wasting banwidth), etc.

Also, I don't actually leave the machines running outside of parties, and updates don't just all happen immediately when you turn the machine on... I'd have to start them up a few days in advance.