Urban Puddle

Getting subversion going isn't really that hard.. the steps aren't that much different whether you're installing on your local Debian machine or deploying to a server where you'll host lots of projects. Here's how you can set up subversion on Ubuntu's Hardy Heron distribution in a few simple steps.

The other day I was playing with Pandora. It's an awesome website but I wanted a way to play it through the remote Ubuntu server I have connected to my stereo. Since that server is headless lots of remote options like xnest and vncserver don't work (without me logging in to the remote server first). I remembered Nomachine's NX server and decided to give it a shot. It works great. Even though the packages haven't been updated for Hardy, the Gutsy packages work fine. Here's how you get it working.

My HAML adventures continue. This time, I'm documenting how to limit the length of a table or table cell. Usually I'd just do something like

 <td width = "500px">

but with HAML you've got to take a different approach. Fortunately it's not that hard:

 %td{:width => 20}=My cell contents

Do yourself a favor, if you get a 502 error using the fastcgi script for nginx, check your /var/log/nginx/error.log file. If you see something that looks like this:

Then make sure you have this line in your php fastcgi_script:

That'll save you a whole lot of head scratching and googling.

Wow, it's impressive that updating from one release of Ubuntu Linux to another can be filed under a Quick Tip. Those guys have done a tremendous job! I think I spent a week setting up and fiddling with FreeBSD before I realized that I couldn't upgrade from 6.3 to 7.0 without pulling my hair out. But this is Ubuntu linux so it's way easier. Here's all you have to do to upgrade from Gutsy to Hardy:

Regular readers know that I've been using Gedit to do most of the text editing now that I've put away my mac in favor of linux. Leaving Textmate was really hard but luckily there are a few great plugins that help smooth the transition. One of the things that was still missing was an easy way to search for code within my project. There is a Find in Documents plugin but it only searches in documents that you already have open. I decided to modify that plugin to create a new one called Find in Files. Read on for the link and to learn a bit more.

I was pretty surprised to find the Xfburn, the xfce cd/dvd burning tool, was not in Debian's Unstable repository. That means you've got to compile it from scratch in order to use it. Compiling from scratch isn't as hard as it sounds.. generally I recommend having a separate folder for the source code. After that it's just a question of the requirements.. so let's work on those.

I recently had to do a fresh installation of Ruby on Rails and Nginx/Mongrel on Hardy Heron server. I compared notes with my last HowTo along the way and decided to write it up in case anybody needs help with the process. If you're struggling with installing Rails, follow along and see if this helps. If you want to scale far and wide on your own I'd suggest popping by Ezra's page and checking out his book. The rest of you.. please read on!

If you followed my previous post on using Gedit to do Ruby Rails development in linux you may have discovered the same annoyance I have. Like Textmate, < will auto-complete the > but unlike Textmate pressing <% will still only complete >. That's led to countless errors where I've accidentally created lines of code like:

<%= link_to "Bar", bars_path >

That lack of a proper closing %> naturally throws an error every time. I guess I'm still not over how textmate would do that automatically for me. Anyway, here's how you correct it.

Ok, I'm going to file this under: stuff you don't care about but I want to keep handy just in case I forget. What is it? I'm talking about dumping a mysql db to a .sql file from the command line. Like everything else, it's really simple if you have the correct syntax. For example if your database is called blogapp, then type:

mysqldump --databases --result-file=blogsqlfile.sql blogapp -u mysqluser -p

Substituting the mysqluser user for your mysqluser (root, mysql, whatever)