developed in window... hosting in a linux box..

Another less obvious one is the fact that the first line in public/dispatch.fcgi contains the path to the Ruby interpreter on Windows and not on Linux.


Should be


or something similar.

The easiest thing to do is to generate the Rails app on the host and then move your files over, making sure not to overwrite dispatch.fcgi. This often ensures the proper execute permissions are set as well.

Or, develop on Linux :slight_smile:

=) Definitely develop on linux. What has been working perfectly for me is using Eclipse and/or RadRails on my Windows box, but store the project on my linux box and access it over a samba share. The only drawbacks to this are some permissions issues that occasionally come up and are easily fixed and that you can't run any of the commands from within your IDE. But how often do you use those anyway? You can just execute them in a shell.

Also, check permissions on dispatch.fcgi if you haven't already.

That shebang line error has gotten me several times before I went to my current setup. Also, it doesn't really tell you what is going on.

Brian Hogan wrote:

Brian Hogan wrote:


#!/usr/bin/env ruby

Or, develop on Linux :slight_smile:

Or dev on Linux with a Samba share to a mounted drive on Windows
running RadRails

But none of this would have fixed the sh-bang problem, which stands at
the exact boundary of Rails's domain. Running Webrick out of
script/server will bypass the shebang on windows, so you can leave it
configured for Linux.

Can't we all just ... get along??

Hi Again,
thanks for ur help....

This code was generare by linux server:

Alfredo_Peru wrote:

Hi Again,
thanks for ur help....

This code was generate by linux server:

AND this by [windows]:


i can't see any difference, any idea???

I see a difference. Same as what others were telling you. Change the
first line. Use the one generated on linux. Neither webrick, nor
mongrel, will care on yer windows machine, but you obviously need it
for your linux environment.