IIRC, the Haml command line utility outputs to another file by default. Since CGI uses stdin/out, you'd have to pass some options to Haml to force it to use stdout, or write a script that acts as the handler and does that for you. Keep in mind that Ruby's CGI interface is really slow w.r.t. Apache -- a new interpreter has to be spawned every time there is a request. I would suggest implementing some sort of caching, perhaps as part of the initial request.
Sean On 7/29/07, Mike Zillion <[EMAIL PROTECTED]> wrote: > > This sounded like a fun idea, but no luck yet. > > I'm thoroughly enjoying HAML and SASS in my Rails application > development. I wanted to use my local haml gem processor as a pre- > processor for .haml files outside of Rails as well, so I could develop > all of my HTML code with this incredible markup. > > The idea is that all files with the suffix .haml should be processed > through haml, while the rest will retain their original processing. I > tried adding the following lines to my .htaccess file (on Dreamhost) > without success: > > AddType text/haml .haml > AddHandler haml-file .haml > Action haml-file /home/mikezillion/.gems/bin/haml > Action text/haml /home/mikezillion/.gems/bin/haml > > This gives me a slow response, and a "Rails application failed to > start properly" error, in a directory where I have not installed any > Rails code. Can anyone spot the problem? If so, I'd love to get this > working! > > -Mike > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
