Hello all, I am a rails newbie so please be gentle. I have checked out a rails project from an SVN repository and am having no luck getting it to operate on my Mac. I can however create rails apps locally and they run just fine. Specifically none of the scripts work (ex. ./script/server). For lack of a better term, is there a symlink created when a project is created using the standard ruby rails projectName command that needs to be made when a non locally created project is checked out from a repository like SVN? Thanks, Brian
Hi Brian, I don''t use a Mac but I think your problems are caused by a wrong "Shebang"-Line. In the first line of the items in the script-directory and also in the dispatchers you find an entry like: #!/usr/bin/ruby18 This must point to a Ruby-Interpreter on your system. So either change this line to a correct path or make a symlink on your system to accomodate the path in the Shebang-Line. (IMHO the better solution because you have only to change one thing instead of several files) Another problem could be that the files have wrong permissions (no executable-rights, should be something like 755). Michael
Here is the error as it appears in my terminal when I run ./script/
server
./script/../config/environment.rb:36:in `require'': No such file to
load -- rubygems (LoadError)
from ./script/../config/environment.rb:36
from ./script/server:42:in `require''
from ./script/server:42
Interesting to note the reference to rubygems. I am not sure why
that is there, or why there would be a call to it when running ./
script/server
Brian
On Jun 15, 2005, at 8:27 AM, Michael Raidel wrote:
> Hi Brian,
>
> I don''t use a Mac but I think your problems are caused by a wrong
> "Shebang"-Line. In the first line of the items in the
script-directory
> and also in the dispatchers you find an entry like:
> #!/usr/bin/ruby18
> This must point to a Ruby-Interpreter on your system. So either change
> this line to a correct path or make a symlink on your system to
> accomodate the path in the Shebang-Line. (IMHO the better solution
> because you have only to change one thing instead of several files)
>
> Another problem could be that the files have wrong permissions (no
> executable-rights, should be something like 755).
>
> Michael
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
Seems like you don''t have Rubygems installed. Rubygems is needed in a standard installation of Rails since it is the preferred distribution method. Maybe your local applications use Rails from the vendor-directory (the tar.gz version) and hence doesn''t need Rubygems. All in all I would recommend to use Rubygems because it is much easier to update Rails and keep all your Rails-applications using the same Rails-version.