Capistrano 3 support

[thaeli]

Currently, this gem is writtend for Capistrano 2. Opening this issue to discuss updating or rewriting for Capistrano 3.

[jondavidjohn]

Maybe clue us in on the potential benefits?

What specifically would be gained by migrating to capistrano 3?

[Idealien]

How about an indication in the docs that it is 2.15.5 or less is required for it as an interim?

Anyone attempting to start from scratch today with capistrano on a new environment will get v3 installed which it does not work with.

http://www.capistranorb.com/documentation/upgrading/

[jondavidjohn]

@Idealien Seems reasonable to me. Also, we do properly declare dependencies in the gemspec, so if you are using bundler this shouldn't be an issue.

[ziz]

A note regarding Capistrano 3 support: currently, cap3 doesn't support git submodules out of the box, making the update - for our primary use case - significantly more complicated.

http://stackoverflow.com/questions/19403138/capistrano-v3-deploy-git-repository-and-its-submodules

[morrislaptop]

I just created a gem for Capistrano 3 with WordPress, it makes the following easy with a click of a button..

• wordpress:db:push - Exports your local database and imports it on remote server
• wordpress:db:pull - Exports your remote database and imports it on your local
• wordpress:db:deploy - Uploads the .sql in your version control and imports in on remote
• wordpress:content:sync - Synchronises your local and remote wp-content/uploads folder so that you have all assets

https://rubygems.org/gems/wordpress-capistrano

Note: It doesn't do symlinking (easy with Cap3) or install WordPress (easy with Composer).

Would love some feedback :)

[cromulus]

Looks like the git submodule issue has been resolved: https://github.com/i-ekho/capistrano-git-submodule-strategy