Capistrano 3 support?

[jfrux]

No description provided.

[ericclemmons]

I was just about to use this project because of all of the issues I had with Cap2 after Cap3's release, but now I'm not sure :)

[andremendonca]

I think the problem is with the dependency "railsless-deploy" with the Cap3

$ cap deploy
undefined method 'instance' for Capistrano::Configuration:Class
/Users/../.rvm/gems/ruby-1.9.3-p484/gems/railsless-deploy-1.1.3/lib/railsless-deploy.rb:1:in '<top (required)>'
/Users/../.rvm/gems/ruby-1.9.3-p484/gems/capistrano-node-deploy-1.2.13/lib/capistrano/node-deploy.rb:2:in '<top (required)>'

[coconitro]

Running into this as well.

[terox]

I'm having @andremendonca problems with Capistrano 3.x. I don't know if it is because this lib is imcompatible with version 3 or I am doing something wrong

[andremendonca]

@terox yes, it's incompatible because of railsless-deploy. To run it with success you will need to use Capistrano 2.x (until we fix it)

[masterkain]

https://github.com/jeffbyrnes/railsless-deploy is unmaintained now.

[andremendonca]

Note at railsless-deploy:
"Capistrano 3 (http://www.capistranorb.com/) doesn't ship with any Railsisms, and is better in almost every measurable way than Capistrano 2 + raileless-deploy. It's time to switch, as I won't be maintaining this Gem anymore!"

Looks like Cap 3 don't need it anymore

[krnekit]

Is there any plans for porting to Capistrano 3?

[heygambo]

I guess not

[shashanksingh]

Aah, I just discovered this after hours of figuring out what went wrong.