Mark Firestone wrote:
> Just looking for some advice, about that boring ruby BBS that I'm always
> rambling on about...

You *asked* for it (advice).

> ...I got the fido, and the smtp working... so I'm looking for a new
> challenge, and it would be nice to actually have someone use the bloody
> thing, so I thought, I'll hook it up to html...
> 
> What's the best way to code this?  If I had designed this thing properly
> from the get-go, I could just write a separate cgi script in e-ruby ...
> as *most* of the data is stored in a postgres database.
> 
> The only stuff that isn't in postgres, is the user data, because it
> would mean major surgery to change this (because of my poor design...
> there are loads of places in the code where the program directly looks
> at data.  
> 
> Anyway, I thought of just building a ruby web server into the program,
> in fact I've started playing with this... so should I do this, or go
> though a major re-write to put the user stuff in postgres?

Yes... that's my advice.  The best way of handling poor design (unavoidable, to some 
extent, when you're not clear on your requirements -- or the problem -- at the start) 
is to REdesign.  Go for it.  Unless you've got a deadline... why not do it right?