From: Corey Jewett <corey@...>
Date: 2005-12-03T01:14:24+09:00
Subject: Re: Problem: Getting Rails to run on apache

A little shell lovin' mixed with Ruby would have seen you through.  
The find command is incredibly powerful, but set aside a day or two  
for digging through the man page. :)

$ cd /root/of/cr-lf/nightmare
$ find . -name '*.conf' -exec ruby -pi -e 'sub(/\r\n/,"\n")' {} \;

That will walk through the tree and exec that ruby bit against every  
file whose name matches *.conf. Note that you need all the gunk all  
the way to the last semicolon.

Corey


On Dec 1, 2005, at 6:32 PM, one man army wrote:

> The oldest problem known to computers...  CR-LF vs \n !
>  but with httpd.conf and .htaccess throwing constant doubt, it
> was never clear. What an exercise in frustration. The files had come
> from Windows, and got sftp'd to the Linux machine. No one sustpected.
>   In anested heirarchy and no suffixes, not that easy to fix, either.
>
>   Here are some resources that opened up during the frantic search:
>
> IRC - not, no one jumped in. REALLY hard to read. Shizo in a window...
>
> <http://lists.rubyonrails.org/mailman/listinfo/rails>
> <http://www.ruby-forum.com>
> <http://wiki.rubyonrails.com/rails/pages>
>
> <http://66.102.7.104/search?q=cache:M7NBv8GLChEJ:www.numberporn.com/ 
> archi
> ves/000118.php+htaccess+error+rails&hl=en>
> <http://httpd.apache.org/docs/1.3/misc/rewriteguide.html>
>
>  hth
>