I am attempting to get a rails 3.0.5 app up and running at http://blastoserver.com/. You can see the errors there. (backtrace)
我试图在http://blastoserver.com/上运行rails 3.0.5应用程序并运行。你可以在那里看到错误。 (回溯)
Any ideas?
有任何想法吗?
4 个解决方案
#1
31
Try gem install bundler
. If that doesn't work my guess would be that you're using two different ruby
or rubygems
installations. The user running the webserver does not see the bundler gem.
试试gem install bundler。如果这不起作用我的猜测是你使用两个不同的ruby或rubygems安装。运行Web服务器的用户看不到bundler gem。
#2
1
Make sure you are running "bundle exec ..." for example: "bundle exec rake -T" instead of just "rake -T". This makes sure that you are executing the command in the context of gem bundle.
确保你正在运行“bundle exec ...”,例如:“bundle exec rake -T”而不仅仅是“rake -T”。这可以确保您在gem bundle的上下文中执行命令。
For more info, look at: http://gembundler.com/
有关详细信息,请访问:http://gembundler.com/
#3
0
I guess you need 'bundle install' or forget rake db:migrate command.
我想你需要'捆绑安装'或忘记rake db:migrate命令。
#4
-1
If seems that it depends on the user. If you run this command on a ssh access as root user make sure not so use the "sudo" in the front. That fixed it for me.
如果看起来它取决于用户。如果您以root用户身份在ssh访问上运行此命令,请确保不要使用前面的“sudo”。那为我修好了。
#1
31
Try gem install bundler
. If that doesn't work my guess would be that you're using two different ruby
or rubygems
installations. The user running the webserver does not see the bundler gem.
试试gem install bundler。如果这不起作用我的猜测是你使用两个不同的ruby或rubygems安装。运行Web服务器的用户看不到bundler gem。
#2
1
Make sure you are running "bundle exec ..." for example: "bundle exec rake -T" instead of just "rake -T". This makes sure that you are executing the command in the context of gem bundle.
确保你正在运行“bundle exec ...”,例如:“bundle exec rake -T”而不仅仅是“rake -T”。这可以确保您在gem bundle的上下文中执行命令。
For more info, look at: http://gembundler.com/
有关详细信息,请访问:http://gembundler.com/
#3
0
I guess you need 'bundle install' or forget rake db:migrate command.
我想你需要'捆绑安装'或忘记rake db:migrate命令。
#4
-1
If seems that it depends on the user. If you run this command on a ssh access as root user make sure not so use the "sudo" in the front. That fixed it for me.
如果看起来它取决于用户。如果您以root用户身份在ssh访问上运行此命令,请确保不要使用前面的“sudo”。那为我修好了。