Homelab

977 readers

1 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 2 years ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

What is a best homelab setup with this hardware? (alien.top)

submitted 2 years ago by favinzano@alien.top to c/homelab@selfhosted.forum

2 comments fedilink hide all child comments

Hello! I'm totally new to this, I want to get a good homelab server for whatever projects I might want to run, install and configure the following network services on my homelab server:

A web server.
A DNS server.
A VPN server.
A NAS server.
A Plex server.
A Docker server.
A Kubernetes server.
A virtualization serve.
A mail server.
An application server.
A proxy server.
An NTP server.

To design my homelab server, I can use the following hardware:

4 Raspberry Pi Model 3B+.
A desktop Dell Optiplex 3050 i5 with 16GB RAM.
A desktop Dell Optiplex 3020 i5 with 16GB RAM
A switch Tplink TL-SF1006P.
A switch Cisco SLM2008
A router Linksys WRT3200AVM.
4 SATA 2.5” 1TB HDD

Do you have any suggestions? Thanks!

top 2 comments

sorted by: hot top controversial new old

[–] nolo_me@alien.top 1 points 2 years ago

I'd throw Proxmox on one of the Optiplexes for virtualization (just my preference, substitute ESXi or whatever floats your boat), TrueNAS on the other and throw the disks in there in RAIDZ1 for your bulk storage. You can use the RasPis to play around with Kubernetes clustering.

[–] ticktocktoe@alien.top 1 points 2 years ago

I mean, part of homelab-ing is getting to do the research and figure out how best to set things up for your specific needs.

Where's the fun in just giving you a blueprint to follow.

I think your first step is to define your goal. Pick 1 or 2 use cases you actually want to execute (not a laundry list of things you could do) and start there.