Re: mod_ruby, ebury and module problem

> Is this not simply a reflection of the fact that each httpd worker process
> has its own Ruby interpreter instance?

That's it on the nose.  There is an alternative to restarting apache though:
you can use load rather than require during development

http://modruby.net/en/doc/?FAQ#Why+are+changes+to+my+library+not+reflected+in+the+server%3F

This causes a performance hit, as for each run through ruby re-reads
the script. Once your code has stabilized and is ready for production,
just replace the load's with require's to see a nice performance
boost.