Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge together both capistrano unicorns (unicorni?) #10

Open
bobbrez opened this issue Mar 10, 2014 · 1 comment
Open

Merge together both capistrano unicorns (unicorni?) #10

bobbrez opened this issue Mar 10, 2014 · 1 comment

Comments

@bobbrez
Copy link

bobbrez commented Mar 10, 2014

Before diving down this path, would it make sense to try to merge both this and @sosedoff's gems together into one for both Capistrano 2 & 3 support under one gem and namespace?

Would @sepastian and @sosedoff be ammenable to that?

My preposal would be:

  • Move capistrano 2 support under lib/capistrano/unicorn/ to model how the other Capistrano gems are modeled (i.e. Capistrano Rails, Capistrano Rbenv, etc... )
  • Implement Capistrano 2/3 detection similar to how Sidekiq and others are doing it.
@toobulkeh
Copy link

👍 looks like this is way outdated... but worth a shot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants