bash: cap: command not found

This post is just an FYI for those trying to use Capistrano on Ubuntu Feisty and running into the same problem I had. I had trouble finding specific information on the topic, thus this post.

I recently tried to use Cap on Ubuntu, and it would not work. I already had ruby and gems installed, having installed them using apt-get. I installed capistrano using the gem install capistrano. I could run gem list and capistrano was installed. All of my other gems worked fine.

When I checked the status of Capistrano using cap -h, I go the error bash: cap: command not found. After doing some searching, I found out how to fix it. Open ~/.bashrc using your favorite text editor. At the end of the file, add these lines:

#The following sets the path for Capistrano
export PATH=$PATH:/var/lib/gems/1.8/bin

Save the file and reboot. Capistrano should work now.

More on Preserving Blogs

I just wanted to mention a couple of things in relation to preserving blogs. First, I wanted to thank Marty Duren, formerly of the influential Baptist blog SBCOutpost. Marty now blogs at ie:missional (I’m not sure what ie stands for, but I hope he’s not endorsing the web browser that dare not name it’s name.) Marty was taking down his SBCOutpost blog, and he graciously provided me with a full digital copy of the blog. I like to think of it as SBCOutpost 2.0, because Marty used to have a Blogger blog before he was converted to WordPress. SBCOutpost is now at version 3.0 as a collabroblog.

Second, I think I am getting closer to an answer on how to grab blogs and store them in a way that will ensure that their arrangement remains intact. I also think that I have a solution for how to ensure that various iterations are distinctly recorded. In other words, I believe that I will be able to do for blogs what the Internet Archive’s Wayback Machine does for regular sites. Better yet, I believe I can do it with entirely free software. I also think that this solution can be used for other web resources. We will see how it turns out, but at this point I have reason to be very hopeful. At this point, I am more concerned with preservation than access. I need to preserve all these “wet blogs” before they dry up.