Odd Git Licensing Message on OSX

Today,IOS 7 dropped to the general public. As usually comes with the release, there was an Xcode update. I updated.  For some time, I’ve been using the git bundled in Xcode as it makes it simpler to get updates as they come with Xcode. Today, that yielded an amusing message. I use git via an alias in my .bashrc A simple version check reveals all:  git –version Oops… git is apparently subject to Apple’s licenses.

Have fun RESTing!

Cheesy post titles aside… I just discovered the very simple but incredibly useful RESTClient at: . It’s a simple Java GUI app for testing out one’s REST services. You can choose your: URL, HTTP method, add any custom headers, add a body for PUT/POST, set auth info, SSL info, and do simple scripting. This is an incredibly useful tool, AND a far cry better than doing it all on the command line with curl.

Here, File File! Nears Release, Gets Attention

I’m taking time away from adding spit and polish to the exciting Here, File File project to say WOO HOO! The whole team (Adam, Buck, and I) are psyched! A few days ago we found out Here, File File is a finalist in the AppsFire Apps Star Awards. And today, The Unofficial Apple Weblog (TUAW) published a great HFF write up. If you haven’t seen our promo video yet, give it a whirl!

Updating RubyGems on Mac OS X 10.5 Leopard

I’m just posting a simple tip today. I was wanting to play around with the very cool SASS meta-language using Compass. The language and tool are implemented in Ruby, which is pre-installed on OS X, but as I discovered, I needed a newer version of RubyGems. I had already known I needed to update Gems, so I was doing the following: Eventually I got errors like this: Turns out, to update RubyGems, one must update the gem system!

Logins with mod_rewrite, Cookies, and Javascript Redux

A while back I posted a simple solution for restricting website access in a situation where HTTP basic authentication couldn’t be used. Not much more to the story, but I did make a few tweaks to my sample code. The mod_rewrite rule and javascript have been a tiny bit improved, so now after a successful login, it will try to redirect you to where you intended to go. (Previously, it always sent the user to /) Also, in the comments I made it MUCH clearer that this is NOT intended to be a secure solution, just a simple way to keep Google and random people out of things.