I think anyone who knows me would say, without a doubt, I’ve changed drastically over the last two years since moving to Seattle. I haven’t changed as a person per se, but I have definitely changed my lifestyle. Here’s a small list of things that my old friends from Michigan simply can’t comprehend.
- I’ve participated in multiple 5k’s and triathlons.
- I own a TV, but don’t have cable. I rarely watch TV and consume 90% of my media online.
- I rarely drive. This last summer I was quite proud of the fact that I didn’t drive my vehicle for 3.5 weeks.
- I don’t eat fast food for the most part.
Now reverse that list and that’s how I lived in the Midwest. The two there that my friends from Michigan are simply astounded about are not driving and not watching TV. This got me thinking as to how much of an impact my move to Seattle has had on the planet. So I took a quiz that calculates my ecological footprint to compare my two lifestyles. I’m happy to report that I’ve saved an entire planet by moving to Seattle! Well, not really, but my ecological footprint went from a score of 23 (5.2 planets to sustain my existence) to 18 (4 planets to sustain my existence).
So, this isn’t really something to cheer about, but it’s definitely an improvement. To top things off I really like the new me. I like training for triathlons, I like being ignorant of pop media and I especially like not having to drive everywhere.
Change is good.
It’s official. As of today I’m employee #20 at Digg. I sent in my resume in September fully expecting not to hear back, but over the course of the last few months it became apparent I was being considered for a position. I didn’t think much of it after not hearing from them for almost a month, but Brian Link sent me an email around the first of the year which turned out to be an official offer.
For those of you that don’t know, Digg is the 19th most visited site on the internet in the United States. It serves up more traffic than Wal-Mart, the New York Times or Best Buy. So, as you can imagine, I’m pretty excited about this opportunity. I’ll be arriving in San Francisco somewhere towards the beginning of February. If you’re in the area and would like to get pints please let me know.
Taking the job means that I won’t be doing any contract work and my open source projects will most likely sit idle for the time being. If you’re interested in maintaining Framework or any of my PEAR packages please let me know.
A client of mine is taking the proactive approach of packaging all of their software using PEAR and distributing it via a custom PEAR channel. I can’t recommend this enough for people that are distributing their PHP code to a number of clients/users.
The problem is that, by default, PEAR channels are consumable by anyone with an internet connection. I sent an email to Greg asking him if there was a way to restrict this and how to go about doing it. As it turns out it’s not only available, but detailed in the free excerpt from his new book The PEAR Installer Manifesto.
There are a number of ways to restrict access. The more complicated approach involves coding a script that handles the authentication and then restricts packages on a per client basis. This is a great way to say client X can install packages A, C and F, while client Y can only install packages B and D.
The route I ended up taking involved simply setting up HTTP-Auth using and
.htpasswd file. Once you have that set up and working you can log in with the following commands.
$ pear -d "pear.mychannel.com" login
Follow the instructions by entering your username and password and you should see a confirmation that you’re logged in. After that you’re allowed to download and install.