Skip to content

Merge together both capistrano unicorns (unicorni?) #10

@bobbrez

Description

@bobbrez

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions