Believe it or do not -- comments checked in

[why the lucky stiff]

Okay, so.  The first round of CGI-related checkins are _in_.  I still 
need to finesse the styles of the default blog.  But everything's 
there.  In fact, even if you're using the old default templates, the 
comments should be easily activated.

=== Installing Comments ===

Obviously, you'll need to update Hobix from CVS first.

If you're starting from scratch, activating the CGI is simple.  It's 
included with the comments-related patches listed upon creation.

To patch an existing blog use:

  hobix patch your-blahhg apache-comments

If you have a heavily modified hobix.yaml, the last patch may fail.  It 
simply adds 'hobix/comments' to your list of requires.  You can do it 
manually.

If you're using custom quick templates and you've customized the `entry' 
template, you may need to add the entry comment stuff manually to your 
custom `entry'.  If comments don't show up when you regen, add:

   <% if entry and not defined? entries %>
     <+ entry_comment +>
   <% end %>

Comments require mod_rewrite.  I've also been testing against lighttpd.  
Here's the rewrite rule I use with lighttpd:

url.rewrite                 = ( 
"^/control((?!/hobix.cgi)[^?]*(\?[\-_a-zA-Z0-9=&%]+$)?|$)"      => 
"/control/hobix.cgi$2" )

=== How Comments Work ===

Hobix now includes an enhanced version of WebApp by Akira Tanaka.  The 
enhancements are related to file uploads and mod_rewrite URLs.

While the rest of your blog remains static, the CGI is placed at 
/control/hobix.cgi.  Plugins loaded in hobix.yaml can expose a `facet' 
(idiotic name, i know) and offer an API through the CGI.

This is the first checkin of this stuff and I still need to pull it all 
together, namely:
* Setting proper group permissions as part of the patch.
* Allowing fastcgi or mod_ruby or WEBrick.  (Supported by WebApp, but 
untested.)

_why