19:57 <Jnco> hi

19:57 <Jnco> Can someone help me to please understand my life working with ROR-- My questions are coming in the way of Gemfile, and Gemfile.lock and setting up a staging environment. I have a very clean install process that I have worked very hard on.. I build the stack ruby/rails/nginx very clean - I pull down my APP from git... The issue I have is when I run bundle install (I created a file inside RAILS_ROOT/.bundle/conf) specifying ubuntu as the home fo

19:57 <Jnco> r bundle), and then start the site, I get errors. (https://ec2-54-243-131-253.compute-1.amazonaws.com/), If the gemfile (list of gems) and gemfile.lock (list exact sources) are existing, why am I having such issues with dependancies and gems and errors, etc after running bundle and starting nginx?

19:58 <havenwood> Jnco: Did you try running `bundle update sprockets` like the error suggests?

19:59 <Jnco> yes

19:59 <Jnco> hi haven :)

19:59 <Jnco> yes then I get another issue

20:00 <Jnco> The bundle currently has rails locked at 3.2.8.

20:26 <Jnco> :)

20:27 <Jnco> and it just goes on an on

21:13 <Jnco> you think its possible my dev isnt running bundle to lock the bundle.lock file?

21:28 <Jnco> guys I have deployed my application using bundle --deployment, the site is messed up. My env is pretty clean, do you think its possible my dev did not perform a 'bundle install' before checking in his code?