Good things come in small packages
Sunday, October 25th, 2009Today is the last day of Energy Saving Week 2009. It’ll also be the last day I’ll be running my 108-watt-when-idle development server. I decided to replace it with the new Mac Mini Server and see if that really lives up to all the marketing hype. Here’s a quick summary:
Pros:
- Sips a measly 13 watts when idle. That’s a whopping 87% energy savings over my old server.
- Hourly back ups to a dedicated hard drive, out of the box. It’s configured as a twin 500 GB set up; one for the OS and the other for Time Machine.
- It’s great as a collaboration server: VPN, VNC, SSH, CalDAV, http/https, Open Directory, per-user/group wikis and blogs right out of the box—but if your DNS server isn’t configured properly (or you have no authority to make changes on it) you’re hosed. Good luck finding help.
- Open Directory + SVN = pure awesomeness; no more mucking around with htpasswd files—users can change their password themselves using a built in web interface.
- Makes a great media server—plays 1080p video full screen very smoothly; even across a (wired gigabit) network share (hosted by a dedicated hardware RAID5 unit).
- It was a hell of a lot faster to set up all those services compared to my old Linux server (I still have nightmares about IPsec and ypserv configuration); and I didn’t have to download/compile anything either. I only had to edit config files to get Apache/SVN working.
Cons:
- You need to administer your own DNS server for everything to work. DNS is painful and very tricky to get right if you haven’t set it up before. Luckily the Tomato router firmware, which includes dnsmasq, is good enough to get everything working. It doesn’t run on all routers, and the ones that it does support only transmit at 802.11g speeds (i.e. 54 Mbits max).
- Kerberos and iCal Server are a huge pain to set up unless you’ve got a fully functional DNS server with fully-qualified forward and reverse mappings for your machines.
- Prone to stealthy name collision problems: if you’ve got a nasty habit (like I do) of creating a local admin account with the same username as your Open Directory user account, you’re in for a whole lot of set-up pain.
- Server Admin keeps overwriting my Apache settings
You can prevent that by putting your stuff in a separate .conffile andIncludeit from the main config.
