Capistrano deployment problems

Question

When I type

cap production deploy

I get

Capfile locked at 3.1.0, but 3.2.0 is loaded

When I uninstall capistrano 3.2.0 I get

Could not find capistrano-3.2.0 in any of the sources
Run `bundle install` to install missing gems.

Me gemfile has

gem 'capistrano', '~> 3.1'
gem 'capistrano-rails', '~> 1.1'

And Capfile

require 'capistrano/setup'
require 'capistrano/deploy'
require 'capistrano/bundler'
require 'capistrano/rails/assets'

What to do in that case?

score 113 · Accepted Answer · answered Apr 16 '14 at 06:33

113

It occurs that config/deploy.rb has lock '3.1.0'.

It was enough to change it to '3.2.0' and now it's working.

answered Apr 16 '14 at 06:33

Kamil Lelonek

14,592
14
66
90

`3.2.1` is now out. Is there a way to specify `3.2.*`? – dave1010 Apr 22 '14 at 15:16
As far as I know you have to specify particular version of capistrano. – Kamil Lelonek Apr 22 '14 at 17:30
20

@squixy You can use operators like `lock '>=3.2.0'` – matthewjewell May 22 '14 at 10:31

score 8 · Answer 2 · answered Jun 27 '14 at 15:00

8

Shouldn't Bundler handle this for you? If you have the version specified in your Gemfile, you can remove the lock version in config/deploy.rb. Then a bundle exec cap production deploy should do the trick.

answered Jun 27 '14 at 15:00

spyle

1,960
26
23

score 0 · Answer 3 · answered Mar 30 '23 at 11:56

0

ERROR:Capfile locked at 3.1.0, but 3.2.0 is loaded

open deploy.rb file find:>>> lock '~> 3.16.0' replace the loaded version to the current version save and exit now run "cap production deploy" Enjoy!

answered Mar 30 '23 at 11:56

Mirza Daniyal

21
2

Capistrano deployment problems

3 Answers3