Parallels provides a nice tool for resizing the file you have chosen as your hard drive for your virtual machine, called the Parallels Image Tool. Unfortunately, Windows is not quite so cooperative, and will not just recognize the resized file as a larger HDD automagically. You need to resize your partition, and Windows doesn't provide any easy ways of doing this.

Googling for a solution, I discovered this very detailed example using Gparted - the Gnome Partion Editor Tool with Parallels. Unfortunately, it is old, and when I tried it the Gparted image refused to boot cleanly, with some sort of error on ... mouse detection, I think. You should just go directly to the Gparted project at SourceForge, and find the most recent stable ISO file to download. While booting, most of the instructions from uneasysilence no longer apply to the new version of Gparted, but I just went with the defaults, and it all worked. Once GParted is up and running, then the instructions from uneasysilence are useful again.

I don't really blog that often. Even when I was going at full tilt, I rarely posted more than 10-12 times a month. So... I don't care about the pagination plugin anymore. I especially don't care when it involves 3 inter-related plugins, at different/conflicting versions!

So I took the easy way out, I'm afraid. Googling for alternatives, I discovered this example pastie, which gives me the month-by-month archive in the sidebar you see now.

See? Who needs pagination?

I've upgraded the blog to Mephisto 0.8.1 Drax. I would have been in serious trouble, had it not been for Rob Seaman's blog. Waves! Hi, Rob. Thanks.

It wasn't just a simple upgrade, in fact, it was pretty freaking complicated. But, since I worked so hard, it should be smooth sailing for the future.

1. Upgrade to new Mephisto, and learn more about Git at the same time (Rob's blog was really useful for that part)
2. Moved from Nginx/Mongrel setup on a Nitix box, to Apache/Passenger on Solaris 10 (SunFire V100). (More on that later)
3. Capified the blog, for better/faster customizations and updates. (Yeeee!!!!!)

Seems like a lot, doesn't it? I thought so too. There was even a couple of days of yak-shaving involved, as I attempted to force certain plugins to work, which were not compatible with 0.8.1. Never mind. The blog is up and running, and it will survive for a day or two without a tag cloud, or pagination. I'll get to it. Promise.

I'll be going to RailsConf next week, and (surprise), I'll also be speaking.
Discussion Panel: Women In Rails
Feel free to comment here, if you aren't going to the conference, but have any good discussion points to add.

I was having a lot of problems with my humongous Rails project lately, with a lot of long delays, build problems, hangs, etc. This all came to a head on Wednesday, when I couldn't do anything without having 3rdRail go and hang on me. But, one of my coworkers who also uses 3rdRail was not experiencing similar problems, so I had to come to the conclusion that the problem was... me.

I've been doing Rails development on my Mac for over 3 years now. This was pre-Leopard, so I had an installed-from-source Ruby that I used. I've been telling myself that this was just smart, because the Ruby that comes with Leopard now is subject to change, any time that Apple cares to issue a software update. I prefer to have my development tools under my own control.

Unfortunately, it seems that this custom Ruby install was the primary difference between my coworker and I, so on Wednesday afternoon I bit the bullet and ripped /usr/local out of my system (bye-bye custom MySQL, Apache, Ruby), and started the painful process of re-installing all the gems I needed using Apple's Ruby (yes, including the Oracle drivers and RMagick.... it wasn't a pleasant afternoon).

Well, now, don't I feel stupid... 3rdRail now builds/rebuilds my project in a reasonable amount of time, without all the stutters and hangs.

So, I'm posting this as an FYI. IF you run into build problems with 3rdRail, it might just be your Ruby install.

This is old information, too, but I hope it is still useful. When I was attempting to install the most recent version of Blackfish (successor to JDataStore) on my Macbook Pro with Leopard, the install failed. Looking in the console for a clue as to what went wrong, I discovered:

08/08/03 12:03:02 PM [0x0-0x30b30b].jds_install[50294] sh: /usr/sbin/lookupd: No such file or directory

This is not an uncommon problem for Leopard. The lookupd command was replaced by dscacheutil. I got around the problem, and got the install to complete successfully by doing this from a terminal:

lori@draco ~
$ cd /usr/sbin
lori@draco /usr/sbin
$ sudo ln -s /usr/bin/dscacheutil lookupd

Make sure you delete that lookupd link when you are finished. The syntax for dscacheutil is similar, but not identical, and you might end up with other weird errors if you forget, and some application tries to use lookupd in a different way.

I know this article is old, but it's worth repeating... over and over. Originally appeared on The Server Side

The Blind Men and the Cloud

It was six men of Info Tech
To learning much inclined,
Who went to see the Cloud
(Though all of them were blind),
That each by observation
Might satisfy his mind

The First approached the Cloud,
So sure that he was boasting
"I know exactly what this is…
This Cloud is simply Hosting."

The Second grasped within the Cloud,
Saying, "No it's obvious to me,
This Cloud is grid computing…
Servers working together in harmony!"

The Third, in need of an answer,
Cried, "Ho! I know its source of power
It's a utility computing solution
Which charges by the hour."

The Fourth reached out to touch it,
It was there, but it was not
"Virtualization," said he.
"That's precisely what we've got!"

The Fifth, so sure the rest were wrong
Declared "It's sass you fools,
Applications with no installation
It's breaking all the rules!"

The Sixth (whose name was Benioff),
Felt the future he did know,
He made haste in boldly stating,
"This *IS* Web 3.0."

And so these men of Info Tech
Disputed loud and long,
Each in his own opinion
Exceeding stiff and strong,
Though each was partly in the right,
And all were partly wrong!

Our Rails application is very dynamic, so page and action caching are not really suitable. But page fragment caching is quite useful. I was implementing this yesterday, and using Greg and Ryan's very useful little tutorial, when I ran into a little difficulty...

Where the heck are the cached fragments?

It was puzzling, but I just couldn't find them, and I was going nuts searching. I thought maybe Passenger was overriding the default location, and stashing them somewhere under Apache. Nope.

Turns out, the answer is fairly simple. The tutorial was written some time ago, and since then the default cache store has changed from :file_store to :memory_store. So you can look for the cache files forever, but you ain't gonna find them.

So, if you want to see caching files in your development environment, you need to have these lines in your config/environments/development.rb file:

config.action_controller.perform_caching = true config.action_controller.cache_store = :file_store, RAILS_ROOT+"/tmp/cache/"