> The reason I say this is that it's the best way to document what users 
> are running into.  That's why I started a tutorial... not that I'm any 
> good at it, but I wanted to pass along a few of the things I learned 
> the hard way. :)

Couldn't agree more. Once you're a proficient user of something, your 
ability to see the rough spots diminishes rapidly. So I didn't catch 
the snag with permissions on log files properly because of it.

But bringing rough spots to the attention of others is a good first 
step, though. So thanks, Carl!
--
David Heinemeier Hansson,
http://www.rubyonrails.org/  -- Web-application framework for Ruby
http://www.instiki.org/      -- A No-Step-Three Wiki in Ruby
http://www.basecamphq.com/   -- Web-based Project Management
http://www.loudthinking.com/ -- Broadcasting Brain
http://www.nextangle.com/    -- Development & Consulting Services