This article will cover installation and setup of Git and Gitweb on Mac OS X. The setup shown here has been done successfully on both OS X 10.6 Snow Leopard and 10.7 Lion.

Although the SCM integration in Xcode 4 is really good I still prefer to interact with git mostly from the command line. I'll show some initial configuration and additional extras, specifically

• Installation
• Initial configuration
• Bash completion and some simple aliases
• Setting up Apache and Gitweb to view your repos in your web browser

After completing this setup procedure you will have the basic config options set for using git from the command line (Terminal) and a way to view your local repos in your web browser.

On February 1, 2011 the latest version of Classic Invaders for iOS went live on the App Store. This update includes Game Center support with custom leaderboard displays.

The game play and difficulty of the game is slightly different on the iPad and iPhone/iPod so different leaderboard categories were created for each and a custom leaderboard displays the top 25 scores of all time for that device type.

The tricky things about setting up AWStats on the Media Temple Grid-Service are that you only have one access log for all your sites, the page requests always have the domain name prepended to them, the logs are processed by Media Temple and then renamed to reflect when the processing is complete, and there is a delay in the processing of these logs which isn't always consistent. These factors have to be accounted for when you setup the AWStats configuration.

Start from the home directory of your (gs) account. Download and decompress the latest stable copy of AWStats.

wget "http://prdownloads.sourceforge.net/awstats/awstats-6.9.tar.gz"
tar zxf awstats-6.9.tar.gz

One of the goals of Classic Invaders from the beginning was that it should run on Windows, OS X, and Linux. One way that this can be accomplished is by using #define sections to separate the platform specific code. However I wanted one code base to compile and run on these platforms without a mess of preprocessor directives and different platform specific code to maintain. By using SDL, Boost, C++, and GCC and staying within the subset of what works on the various platforms I was able to achieve this.

SDL is the main ingredient that makes this possible, but you still have to get development environments setup. Check out the series of articles I wrote Setting up for development with SDL for some specific instructions.