For real. Sorta. I gave a lightning talk about God+Merb at this year’s Ruby Hoedown in Huntsville, Alabama. It’s not much, but here is my 5 min. rundown of what I’ve done to god, and how I use it. It’s available here from the confreaks website.
Open Source, ruby
Ruby Hoedown
Ruby on Rails
RSpec Stories On Rails
Using a story to drive your development tasks is a good idea, even when there is only 1 team member. Writing stories helps you stay focused on the requirements without getting side-tracked into something that isn’t working toward the end goal of your app. There’s always time for script.aculo.us later! Using RSpec stories also means you have tests to run against your code so you know that fixing something probably didn’t break something else.
First thing you want to do is get the RSpec on Rails plugin installed, and generate the RSpec code.
$ ./script/plugin install git://github.com/dchelimsky/rspec.git
$ ./script/plugin install git://github.com/dchelimsky/rspec-rails.git
$ ./script/generate rspec
Stories are broken down into 2.5 files:
- 1. The Story file - Where the plain text story resides
- 2. The Step file - Where the different steps in your story are defined.
- 2.5 The Story runner file - The ruby code that kicks everything off.
Git
Creating a Remote Git Repository
Having a local Git repository is great, it lets you keep versioned copies of your work, and doesn’t take up much space. But if you need to share your repository with someone else, such as with a development environment, you quickly find you need a simple way of keeping the repository up to date, and allowing access to other people. Email and thumb drives are soon not enough to keep up with the pace of development. What you need is a server to keep all the information in.
I’m going to show you how we have things setup, and hopefully guide you in your quest to have a remote repository that works for you.
Assumptions:
First off I’m going to assume you have a server setup somewhere, and that you have ssh and root(or sudo) access. This is written for FreeBSD, but the steps should be similar enough on pretty much any Linux or BSD distro.
Read more…
Open Source
Compiling MySQL Native Bindings on OS X + MacPorts
Playing around with the partitions on my mac yesterday, i accidently deleted the efi partition (dumb of me, i know), but I figured it was about time for a reload, so i just sucked it up and wiped the mac clean.
Going through and installing all the stuff i needed for development, i ran into a problem installing the native mysql bindings for ruby.
General Computing
Slow Samba on OS X
I’ve been using FreeNAS for about a year now to host content for my XBMC and other things, such as my iTunes Library and family photos. One thing that’s always bothered me is on Windows, it’s been fast and responsive, but on my MacBook Pro (running tiger) it crawls at about 150-200kbps, even when plugged into the same switch as the NAS.
Today, I was copying over an audio file (AK1200 Live in San Francisco to be exact) and i finally decided enough is enough. Finally found a way to fix it, that was apparently posted in 2005 (i’m a little slow). It’s not the actual blog post, but the comment under it. So, just in case anyone is having the same problem, here is the solution.
This didn’t work for me, but setting the sysctl parameter net.inet.tcp.delayed_ack to 0 did! For me, the results were dramatic: drag-and-drop of a 100MB .wav file from the samba server took 45 minutes before the fix, and < 2 minutes after the fix. Wahoooo!
Found the info here: http://julipedia.blogspot.com/2006/02/samba-performance-under-mac-os-x.html
[in case that link vanishes, here's the short version:
use 'sudo sysctl -w net.inet.tcp.delayed_ack=0' on command-line to try it (persistent until reboot) and put the line
'net.inet.tcp.delayed_ack=0' in /etc/sysctl.conf to fix it 'permanently' -- note: I haven't tested the latter yet. I had to create the sysctl.conf file, and haven't rebooted yet]
and a good discussion of *why* it works, starts at the bottom of that same blog entry, then links to the crux of the problem here:
http://mail-index.netbsd.org/tech-net/2003/01/28/0004.html
[It's a TCP bug inherited from the FreeBSD stack - the same bug was fixed in NetBSD back in 1997, and Apple has known about it since before Jaguar release]