Apr 20

Erzeugt man unter Mac OS X 10.5 (Leopard) mit dem Befehl “rails anwendungsname” eine neue Anwendung und versucht diese nach “cd anwendungsname” anschließend mit “ruby script/server” zu starten, so erhält man in der Standardkonfiguration die folgende Fehlermeldung:

$ rails anwendungsname
$ cd anwendungsname
$ ruby script/server
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
Exiting
/Users/username/Sites/anwendungsname/config/environment.rb:44: undefined method `time_zone=' for #<Rails::Configuration:0x1242df8> (NoMethodError)
from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/initializer.rb:47:in `run'
from /Users/username/Sites/anwendungsname/config/environment.rb:13
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:342:in `new_constants_in'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require'
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.4/bin/../lib/mongrel/rails.rb:147:in `rails'
... 20 levels...
from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/commands/server.rb:39
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require'
from script/server:3

Die installierte Version wurde von “gems.rubyonrails.org” geladen die für Entwickler gedacht ist, deshalb entfernt man diese Quelle mit dem Befehle “gem sources -r http://gems.rubyonrails.org” (je nach Konfiguration auch: “gem sources -r http://gems.rubyonrails.org/”) aus dem Cache:

$ gem sources -r http://gems.rubyonrails.org
Bulk updating Gem source index for: http://gems.rubyonrails.org/
http://gems.rubyonrails.org removed from sources

Danach muss man die alten “fehlerhaften” Versionen mit dem Befehle “gem uninstall rails” deinstallieren:

$ gem uninstall rails
Select gem to uninstall:
1. rails-2.0.2
2. rails-2.0.2.9216
3. All versions
> 3
Successfully uninstalled rails-2.0.2
Successfully uninstalled rails-2.0.2.9216

Abschließend muss noch eine brauchbare Version von Rails mit “sudo gem install rails” installieren, schließlich wollen wir damit auch arbeiten:

$ sudo gem install rails --include-dependencies
Password:
INFO:  `gem install -y` is now default and will be removed
INFO:  use --ignore-dependencies to install only the gems you list
Bulk updating Gem source index for: http://gems.rubyforge.org/
Successfully installed rails-2.0.2
1 gem installed

Erzeugt man nun eine neue Anwendung und startet diese, sollte alles wie gewünscht funktionieren:

$ ruby script/server
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no restart).
** Rails signals registered.  HUP => reload (without restart).  It might not work well.
** Mongrel 1.1.4 available at 0.0.0.0:3000
** Use CTRL-C to stop.

Auch die Ausgabe im Browser liefert das gewünschte Ergebnis:



Verwandte Beiträge

Kommentar schreiben