Yay! I got apache upgraded to 2.2 from 2.0. It was a lot easier after I was told by Aaron that Feisty has 2.2 in their apt-get repositories. I just had to update from Dapper to Feisty. Prior to updating I did have to comment out all of the repositories I had added to my /etc/apt/sources.list. I was running into some broken wgets otherwise.
After commenting out the additional repository lines, I just followed the steps here and viola! apache2.2 comes up.
I did have to reinstall mod_jk for apache2.2 but that was a easy.
Well, I got to like the second step before I hit another roadblock. Looks like kodefoo’s repository only supports binary-i386 releases. Too bad my slice is on an AMD64 machine which means I need the amd64 release. I guess if I want to cluster mongrel with apache, I’ll have to compile from source. Sigh…
Prior to hitting this road block, I ran apt-get remove apache2 and it didn’t remove apache2 from my slice even though it said it did. So that’s a little confusing. I continued with the kodefoo tutorial regardless until I came across the problem noted above. I’ll eventually have to figure out how to do a clean remove of apache2.
At this point, I think I am just going to try to get a single mongrel served up through apache2. Hopefully, this will be easier…
Paul Graham just wrote a very insightful piece that I hope companies take note of. The start of the essay speaks to how important it is for programmers to have the ability to store the entire context of a problem in their head so they can navigate to all the pieces they need to work on. This is key for solving big problems and facilitates effective productivity. Graham goes on to provide 8 ways to help programmers to do this.
One of the ways he suggests is to work in small groups. At my work, we do a lot of pair programming and sometimes 3-way programming. I find this to be extremely effective for the way I code. I enjoy being able to constantly ask if this is the right way to approach a problem or am I understanding the problem correctly. With pair programming, I get immediate feedback by my teammate(s) and it helps to spread knowledge of the code base without having to go through code reviews.
The second half of the essay is what really inspired me to write this post. Graham makes the claim that companies deliberately try to do things wrong when it comes to dealing with programmers.
One of the defining qualities of organizations since there have been such a thing is to treat individuals as interchangeable parts.
It’s not merely true that organizations dislike the idea of depending on individual genius, it’s a tautology. It’s part of the definition of an organization not to.
The weakest point in big companies is that they don’t let individual programmers do great work.
Moral of the story: Create a work environment where developers are truly valued. They are the problem solvers. They are the closest to the product. They are the ones bubbling with ideas. Listen to them. Don’t act like a big company no matter what your size is. This is how to beat your competitors.
So I’ve still been trying to get mod_proxy_balancer installed. I tried just getting a compiled mod_proxy_balancer.so and drop it into my existing apache2 install but upon start up I get:
Cannot load /usr/lib/apache2/modules/mod_proxy_balancer.so into server: /usr/lib/apache2/modules/mod_proxy_balancer.so: undefined symbol: proxy_hook_post_request
Looks like I have to do a clean uninstall and reinstall of apache2 from source. I’ll have to resetup svn (svn_dvn) and all my virtual hosts so this blog is going to be MIA while I go through this process.
I can’t wait until the Ubuntu repositories update apache2 to 2.2 so mod_proxy_balancer support will be as simple as apt-get install apache2.
I think the next step is to remove my existing apache2 install and give kodefoo’s tutorial a shot.