Databases
StackOverflow2013
Postsdbo
POInstalling Gems with Bundler == Big problem
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POInstalling Gems with Bundler == Big problem
    text
    copied!<p>If I run <code>bundle install</code> , everything passes. I reboot nginx, and when I visit the site I see the passenger error with this :</p> <pre><code>git://github.com/spree/spree.git (at master) is not checked out. Please run `bundle install` (Bundler::GitError) </code></pre> <p>My gemfile :</p> <pre><code>source 'http://rubygems.org' gem 'rails', '3.0.3' gem 'spree', :git =&gt; 'git://github.com/spree/spree.git' gem 'haml' gem 'ruby-debug' gem 'sqlite3', :require =&gt; 'sqlite3' gem 'ckeditor', '3.4.2.pre' gem "aged_revolt", :require =&gt; "aged_revolt", :path =&gt; "aged_revolt" gem "spree_easy_contact", '1.0.2', :path =&gt; "#{File.expand_path(__FILE__)}/../vendor/gems/spree_easy_contact-1.0.2" gem "honeypot-captcha" </code></pre> <p>When I run <code>bundle show spree</code> :</p> <pre><code>/home/shadyfront/.rvm/gems/ruby-1.8.7-p330@revolting_gems/bundler/gems/spree-44e4771f3a2a </code></pre> <p>Any idea how/why this is occuring and how I can get past this ?</p> <p>This is my nginx.conf :</p> <pre><code>env GEM_HOME=/home/shadyfront/.rvm/gems/ruby-1.8.7-p330@revolting_gems; worker_processes 1; events { worker_connections 1024; } http { access_log /home/shadyfront/logs/user/access_revolting_age.log combined; error_log /home/shadyfront/logs/user/error_revolting_age.log crit; include mime.types; passenger_root /home/shadyfront/webapps/revolting_age/gems/gems/passenger-2.2.15; passenger_ruby /home/shadyfront/webapps/revolting_age/bin/ruby; sendfile on; passenger_max_instances_per_app 1; rails_spawn_method conservative; passenger_max_pool_size 2; server { listen 56943; passenger_enabled on; root /home/shadyfront/webapps/revolting_age/releases/20110215175319/public; server_name localhost; } } </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload