This go around I am incorporating some recent additions to the stack, notably Homebrew and rbenv. These additions, as well as a few other changes are being made to simplify things and to follow the latest best practices.

The steps I followed to setup my development environment are as follows:

1. Install Homebrew – the missing package manager for OSX. Luckily I didn’t run into any issues installing Homebrew. Homebrew greatly simplifies installing some of the more difficult bits and pieces on OSX.

2. Install rbenv – This differs from my previous use of RVM. While I really liked RVM, the simplicity of rbenv convinced me to switch. Again, no real issues with installation (that is the beauty of a single purpose, simple tool). I didn’t use Homebrew to install rbenv, but in the future I will. With rbenv I also installed the companion ruby-build which simplifies the process of installing various Ruby versions.

3. Install PostgreSQL – While I am a longtime fan of MySQL, it’s acquisition by Oracle combined with the herd moving towards Postgres made me take the plunge. All in all it has been a fairly straightforward process. There is one caveat, when installing Postgres on OSX Lion (which replaced it’s bundled install of MySQL with Postgres) you need to make a minor change to the system paths so that Postgres loads from your installation and not the built in one. I followed the tips from a few blogs and updated /etc/paths, placing “/usr/local/bin” at the top. That one tip, combined with following the instructions provided by Homebrew (accessible via “brew info postgresql”) will get Postgres up an running in no time.

That is basically it! I think this is a really clean and simple install that makes my apps fairly portable. I am using Bundler to manage my Ruby Gems in conjunction with the rbenv-gemset plugin. I could just rely on Bundler, but I prefer to have the gems sandboxed in a separate gemset (for now).

After cloning from GitHub and running “bundle install” and the various rake database tasks I was up and running in development mode with relative ease. One of the wonders of the open source software community is that there seems to be a real emphasis on continuous and meaningful improvement. With each major iteration the tools I am using are becoming both more powerful and easier to use. I was able to get my development environment up and running in about an hour (less if my memory were better). That pales in comparison to some of the herculean efforts required in the past.

Red Bull Racing was finally able to lock out the top two positions in qualifying, although Webber was no match for Vettel in qualifying, or in the race for that matter. Vettel truly seems to be in a class of his own at the moment. Nico Rosberg was able to hoist his improving Mercedes GP car to the third step of the podium with Lewis Hamilton’s McLaren and Fernando Alonso’s Ferrari rounding out the top five in qualifying. Behind the top five were the usual players in their usual order (with some slight shuffling here and there). One exception was Kamui Kobayashi who’s Sauber failed to set a qualifying time and resulted in Kobayashi starting at the back of the grid. Luckily for Kobayashi he had posted times in practice well within 107% of the quickest time set in the first qualifying period which prompted the race stewards to allow him to start despite not setting a time.

The race start was rather tidy and saw a few position changes throughout the field mostly due to the differences in grip from the two starting lanes. Ferrari’s Fernando Alonso was finally able to get a good start and found himself not losing places as he has done in the previous races this season. One interesting insight I read after the race was in regards to the lack of chaos and crashes that have typically accompanied Grand Prix starts. The author surmised that with the passing opportunities afforded by the Drag Reduction System (DRS), Kinetic Energy Recovery System (KERS) and the Pirelli tires this season the driver’s no longer feel the desperation they once did to make up places at the start of the race. With the various changes this season, it seems the drivers are willing to wait and see how the various strategies play out in favor of trying to squeeze a rocketing F1 car into a tiny gap through the first corner. The result of this is that cars are no longer being taken out in first corner melees this season, which results in more cars battling throughout the race.

The race itself was a combination of confusing strategic wrangling and pointless “push to pass” scenarios using the Drag Reduction System (DRS). One exception to all of this was Kamui Kobayashi’s fantastic drive from dead last to finally ending up 10th and securing a Championship point for himself and Sauber. The usual players found themselves in more or less their usual places by the time the race ended. Sebastian Vettel drove a faultless race from Pole Position to the top step of podium. The Red Bull of Mark Webber finished second after battling Alonso’s ascendant Ferrari throughout the race finding themselves trading places a couple of times courtesy of the DRS “push to pass” button and tire degradation differences. A Red Bull 1-2 followed up with Ferrari finally capitalizing on their consistently high race pace rounded out the podium. The rest of the field crossed the line in the expected order with Renault, McLaren and Mercedes GP trading places to fill in the rest of the top 10 with Sebastian Buemi’s Torro Rosso and Kamui Kobayashi’s Sauber being the major exceptions.

The true star of this race was, and typically is, the Istanbul Park circuit. Like most great circuits there is one defining feature that sets them apart from the rest and in Istanbul this is Turn 8. Watching Formula One cars pull over 4Gs for 4-5 seconds while speeding around this 3-4 apex turn is phenomenal. Unfortunately the nature of this great track was slightly overshadowed by the contrived manner of passing being created by some of the rule changes this season. Particularly the Drag Reduction System (DRS). Perhaps a change in the DRS zone’s location or length could have alleviated some of the ridiculously easy passes we saw, but altogether this system is beginning to irritate some spectators, myself included. In season’s past when one driver passed another it meant something in the overall battle for the season’s championship. With the DRS the passes are no more meaningful than the ones we all make on our daily commutes. I would have rather seen the DRS zone moved between turns 7 and 8. Imagine the courage and skill required to effect a pass while setting up to go through turn 8! Now that would be a spectacle.

Sebastian Vettel of Red Bull Racing started on pole, led nearly every lap, and finished in first place to continue where he left off after winning the World Driver’s Championship in 2010. His teammate, Mark Webber did not fare so well in his home race managing to secure 5th place despite starting a promising 3rd. McLaren looked much more their speedy selves in the race compared to winter testing with Lewis Hamilton finishing second and Jenson Button putting in a strong performance despite managing only a 6th place finish likely due to a drive-through penalty incurred after passing Felipe Massa’s Ferrari off track. Fernando Alonso qualified well for Ferrari in 5th. A lack lustre start found Alonso falling from 5th to 9th place after the dust settled from the start. Fernando Alonso put in an impressive drive to eventually claw his way back to an impressive 4th place by the end of the race. His Ferrari teammate likewise gained a single position throughout the race to finish 7th. One standout from the usual players at the front of the grid was Lotus Renault’s Vitaly Petrov. A phenomenal start and flawless race landed Vitally on the 3rd step of the podium, a first for Vitaly, a first for a Russian and undoubtedly a relief for Lotus Renault whose championship dreams were surely being questioned with the (hopefully temporary) loss of Robert Kubica in an unrelated rally accident during winter testing.

The anticipation leading up to the race was heightened due to the rule changes enacted for the 2011 season. As is usually the case with each new season a number of changes to the rules that govern F1 have been enacted in the name of safety, cost-savings and the ever elusive goal of increasing overtaking in F1. For the 2011 season, two rules stand out and have been the topic of much debate in the off season. New for 2011 is the Drag Reduction System (DRS) and the re-introduction of the Kinetic Energy Recovery System (KERS), both of which aim to make overtaking easier.

The new DRS has been implemented to aid a following cars ability to overtake another at the end of a long straight. In my opinion this system is contrived and will most likely be relegated to the waste bin in the near future. The DRS is an artificial means to correct a problem that not everyone agrees even exists. There has long been a debate in F1 circles that it is too difficult for one car to overtake another in F1. While many casual observers (read: new, lucrative TV eyeballs) may find the apparent lack of overtaking boring the seasoned fan appreciates the difficulty and marvels at the skill and craftsmanship required to overtake in an F1 car. Time will tell if the DRS is successful or not, but I am not betting on it.

The second major technological change for this year is the re-inclusion of KERS. While KERS was available last year, the teams had all agreed not to use it. There are many reasons for the exclusion of this technology from last year’s cars, but I am glad that it is back for 2011. KERS allows the cars to store otherwise wasted kinetic energy in onboard batteries in order to provide 6 seconds worth of an additional 80 BPH per lap. I for one applaud the inclusion of this technology, but I am truly at a loss as to why the FIA has placed such strict limits on it’s application. For me Formula One is a wondrous mixture of technological wizardry and sublime driving skill. Placing limits on KERS only limits what the engineers and drivers in F1 are capable of. If left unchecked they would be able to extract enormous amounts of power from the kinetic energy of the car and would certainly be able to produce more than a mere 6 seconds of it per lap. I know that the limits have been put in place to save money, but I would rather see money saved in other areas to allow KERS to truly blossom.

All in all the season is off to an exciting start. The players are the same at the top and only time will tell if their order will follow from last year as well. Red Bull Racing look dominant, but McLaren, Ferrari and Lotus Renault do not seem too far off. As with every F1 season there are two races happening simultaneously, the race to develop one’s car at a blistering pace in hopes of outdoing one another on a technical level and the race between the drivers on the track on Sunday. Therein lies the true magic of F1, the combination of driving skill and engineering excellence.

I followed a few tutorials, all to no avail:

• Gittr
• RailsTips
• And others…

So, what did I learn? Dreamhost doesn’t necessarily have the gems you need, or the dependencies for the gems you need. What I needed to do was to “vendor” a copy of Sinatra, but not the most recent version which has a dependency for a gem called “tilt”. So I took a stab in the dark, picked an older version (0.9.4) and after some de-hacking from previously failed attempts to get things working the site is up and live using Sinatra on Dreamhost.

My final configuration is very similar to the first to tutorial links above, the key part for me was vendoring the correct version of Sinatra.

via: Mashable

Twitter has announced the TweetButton, as seen at the bottom of each post here! Super simple to implement. I am thinking that I prefer Twitter over many other social entities. It is simple and allows for quick and easy communication. I feel like most other social tools are way too cumbersome and try to do too much.

Get your very own TweetButton here: http://twitter.com/goodies/tweetbutton

• Installing MySQL on Snow Leopard
• Installing Git on Snow Leopard
• Installing Ruby, RubyGems, and Rails on Snow Leopard

Recently, however, I have found a new way to install Ruby, RubyGems and Rails. This new method allows for a simple installation and switching between different versions of Ruby. Enter, Ruby Version Manager (aka RVM). Once installed and configured, installing Ruby is as simple as:

rvm install 1.9.1

I was introduced to this magical tool via a screencast from Ryan Bates on Railscasts entitled: Rails 3 Beta and RVM

In addition, the House bill would extend Medicaid eligibility to 150 percent of the poverty line ($33,000 for a family of four), while the Senate plan lifts the threshold to 133 percent of poverty (family income: $29,000).

Now, read that again, Medicaid coverage will be extended to households of 4 that make less than $33,000. Why doesn’t Congress account for the widely varied cost of living when accounting for income levels? $33,000 in California does not go nearly as far as it does in rural Alabama. Why should we Californians be subjected to the same taxation rates if we are only going to be short changed on the benefits?

To continue using Google Earth, you must accept the new Google privacy policies and allow Google Software Update to run in the background on your computer.

This smells funny to me… I like most of Google’s products, but I don’t enjoy having extra stuff forced upon me. While I imagine that Google’s Software Update service is probably fine and will most likely not cause any problems, I would like to at least be presented with an opportunity to opt-out of this.

Specifically, when I would try to access a site in development mode I would get an error from Passenger that “Rails 2.3.4 could not be found”. I also noticed that on reboot my PATH wasn’t being loaded properly either so the system could not find MySql, Ruby, or RubyGems.

I tried placing the path information that, according to the instructions goes in ~/.profile into my ~/.bash_profile.

Now when I restart the system, MySQL and Ruby on Rail can be found! Passenger is working now as well. I am not sure if there was a change in the way Snow Leopard loads bash profiles or if there is just a problem with my installation that was preventing it from working when the PATH was specified in ~/.profile, but it’s all working now so hopefully this will help someone else.