Unable to update gems on production server
Solution 1
The instructions are probably a bit confusing. It's saying that you've modified your Gemfile
on your development machine and just pushed those changes rather than running bundle install
BEFORE committing the changes.
By running bundle install
you will update your Gemfile.lock
file. This should be pushed to your server as it's more important than Gemfile
. Consider the Gemfile
the plans for the Gemfile.lock
file.
Always remember to:
- Run
bundle install
if you change yourGemfile
, even just to make sure. If it's too slow, pass--local
through which forces it to only use local gems to resolve its dependencies. - Commit both the
Gemfile
andGemfile.lock
file to your repository - Deploy both the
Gemfile
andGemfile.lock
to your production servers to ensure that they're running the exact same dependencies as your development environment.
Running bundle update
by itself can be construed as dangerous that will update all the dependencies of your application. It's mainly dangerous if you don't have solid version numbers specified in the Gemfile
. I wrote about it here.
Solution 2
FWIW I had this problem and fixed it by removing some conditional statements from my Gemfile (conditionals on OS) and rerunning bundle.
Solution 3
FYI: You can also get this error if you use source blocks like this:
source 'https://rails-assets.org' do
gem 'rails-assets-jquery'
end
You'll see an exclamation point in the Gemfile.lock for this gem:
rails-assets-jquery!
Just define the additional source normally, i.e.
source 'https://rails-assets.org'
gem 'rails-assets-jquery'
(BTW cf. here about using multiple gem sources.)
Solution 4
This can be caused by an old version of the bundler gem on the server you're deploying to (in this case production). Logging into the server and running a gem update bundler
resolved the issue for me. The server I was deploying to was running version 1.7.4 and the current version was 1.9.
Solution 5
I had an issue with my production server still using an old version of a gem, even though the Gemfile.lock showed the correct, updated version. My production server was running on Unicorn - and shutting down / starting it back up again fixed the issue - instead of sending the HUP signal, which did jack all to fix the issue.
pcasa
Updated on July 09, 2022Comments
-
pcasa almost 2 years
Can not update gems on production server.
I've tried
bundle install --deployment
andbundle install --without development test
But keep getting:
You are trying to install in deployment mode after changing your Gemfile. Run `bundle install` elsewhere and add the updated Gemfile.lock to version control. If this is a development machine, remove the Gemfile freeze by running `bundle install --no-deployment
EDIT
I don't know if this is correct, but needed a quick fix. I ran
bundle install --no-deployment
thenbundle update
then ranbundle install --deployment
again