Selfhosted

I would documented everything as I go.

I am a hobbyist running a proxmox server with a docker host for media server, a plex host, a nas host, and home assistant host.

I feel if It were to break It would take me a long time to rebuild.

aa

I would have taken a deep dive into docker and containerised pretty much everything.

I wouldn't change anything, I like fixing things as I go. Doing things right the first time is only nice when I know exactly what I'm doing!

That being said, in my current enviroment, I made a mistake when I discovered docker compose. I saw how wonderfully simply it made deployment and helped with version control and decided to dump every single service into one singular docker-compose.yaml. I would separate services next time into at least their relevant categories for ease of making changes later.

Better yet I would automate deployment with Ansible... But that's my next step in learning and I can fix both mistakes while I go next time!

I should have learned Ansible earlier.

Docker compose helped me get started with containers but I kept having to push out new config files and manually cycle services. Now I have Ansible roles that can configure and deploy apps from scratch without me even needing to back up config files at all.

Most of my documentation has gone away entirely, I don't need to remember things when they are defined in code.

Go with used & refurb business PCs right out of the gate instead of fucking around with SBCs like the Pi.

Go with "1-liter" aka Ultra Small Form Factor right away instead of starting with SFF. (I don't have a permanent residence at the moment so this makes sense for me)

For me:

• Document things (configs, ports, etc) as I go
• Uniform folder layout for everything (my first couple of servers were a bit wild-westy)
• Choosing and utilizing some reasonable method of assigning ports to things. I do not even want to explain what I need to do when I forget what port something in this setup is using.

Buy an actual NAS instead of a rats nest of USB hub and drives. But now it works so I'm too lazy and cheap to migrate it off.

I already did a few months ago. My setup was a mess, everything tacked on the host OS, some stuff installed directly, others as docker, firewall was just a bunch of hand-written iptables rules...

I got a newer motherboard and CPU to replace my ageing i5-2500K, so I decided to start from scratch.

First order of business: Something to manage VMs and containers. Second: a decent firewall. Third: One app, one container.

I ended up with:

• Proxmox as VM and container manager
• OPNSense as firewall. Server has 3 network cards (1 built-in, 2 on PCIe slots), the 2 add-ons are passed through to OPNSense, the built in is for managing Proxmox and for the containers .
• A whole bunch of LXC containers running all sorts of stuff.

Things look a lot more professional and clean, and it's all much easier to manage.

Instead of a 4-bay NAS, I would have gone with a 6-bay.

You only realize just how expensive it is to expand on your space when you have to REPLACE HDDs rather than simply adding more.

I would have gone with an Intel CPU to make use of iGPU for transcoding and probably larger hard drives.

I also would have written down my MariaDB admin password... Whoops

Actually plan things and research. Too many of my decisions come back to bite me because I don't plan out stuff like networking, resources, hard drive layouts..

also documentation for sure

Setup for high availability. I have a hard time taking things down now since other people rely on my setup being on.

More ram 🐏

I always redo it lol, which is kind of a waste but I enjoy it.

Maybe a related question is what I wish I could do if I had the time (which I will do eventually. Some I plan to do very soon):

• self host wireguard instead of using tailscale
• self host a ACME-like setup for self signed certificates for TLS and HTTPS
• self host encrypted git server for private stuff
• setup a file watcher on clients to sync my notes on-save automatically using rsync (yes I know I can use syncthing. Don't wanna!)

I'd have stuck with ZFS.

Make sure my proxmox desktop build can do GPU passthrough.

I'm generally pretty happy with it, though I'd have used podman rather than docker if I were starting now.

I'd use Terraform and Ansible from the start. I'm slowly migrating my current setup to these tools, but that's obviously harder than starting from scratch. At least I did document everything in some way. That documentation plus state on the server is definitely enough to do this transition.

My current homelab is running on a single Dell R720xd with 12x6TB SAS HDDs. I have ESXi as the hypervisor with a pfsense gateway and a trueNAS core vm. It's compact, has lots of redundancy, can run everything I want and more, has IPMI, and ECC RAM. Great, right?

Well, it sucks back about 300w at idle, sounds like a jet engine all the time, and having everything on one machine is fragile as hell.

Not to mention the Aruba Networks switch and Eaton UPS that are also loud.

I had to beg my dad to let it live at his house because no matter what I did: custom fan curves, better c-state management, a custom enclosure with sound isolation and ducting, I could not dump heat fast enough to make it quiet and it was driving me mad.

I'm in the process of doing it better. I'm going to build a small NAS using consumer hardware and big, quiet fans, I have a fanless N6005 box as a gateway, and I'm going to convert my old gaming machine to a hypervisor using proxmox, with each VM managed with either docker-compose, Ansible, or nixOS.

...and I'm now documenting everything.

Not accidentally buy a server that takes 2.5 inch hard drives. Currently I'm using some of the ones it came with and 2 WD Red drives that I just have sitting on top of the server with SATA extension cables going down to the server.

I already have to do it every now and then, because I insisted on buying bare metal servers (at scale way) rather than VMs. These things die very abruptly, and I learnt the hard way how important are backups and config management systems.

If I had to redo EVERYTHING, I would use terraform to provision servers, and go with a "backup, automate and deploy" approach. Documentation would be a plus, but with the config management I feel like I don't need it anymore.

Also I'd encrypt all disks.

Get a more powerful but quieter device. My 10th gen NUC is loud and sluggish when a mobile client connects.

I would spend more time planning and understanding docker. My setup works, but it's kinda messy

I'd make my own nas.

I'd put my storage in a proper nas machine rather than having 25tb strewn across 4 boxes

Would've used NixOS

I'd plan out what machines do what according to their drive sizes rather than finding out the hard way that one of them only has a few GB spare that I used as a mail server. Certainly document what I have going, if my machine Francesco explodes one day it'll take months to remember what was actually running on it.

I'd also not risk years of data on a single SSD drive that just stopped functioning for my "NAS" (its not really a true NAS just a shitty drive with a terabyte) and have a better backup plan

Not go as HAM on commercial server hardware. iLO is really nice for management though...

I have ended up with 6x 2TB disks, so if I was starting again I'd go 2x10TB and use an IT mode HBA and software RAID 1. I'd also replace my 2x Netgear Switches and 1x basic smart TP-Link switch and go full TP-Link Omada for switching with POE ports on 2 of them - I have an Omada WAP and it's very good. Otherwise I'm pretty happy.