Cap3

[leehambley]

I've just had a mailing list question for Capistrano regarding the integration. Looks like your Gem is targeting the 2.x code branch which was EOL'ed recently.

There's a new rewrite, and I'm not sure how you can integrate, if you are even interested in doing so.

I just wanted to make you aware of the issue, I've cross-posted this issue reference to the list's OP, too:

• Mailing list thread: https://groups.google.com/forum/#!topic/capistrano/bdZ_17b32fI

Thanks!

[jondavidjohn]

Cool, thanks for the heads up!

The gem itself isn't really "targeted" at a particular version of capistrano, we just expose some one off methods to control the output.

So really the question is how would someone control the verbosity of the output similar to the 2.x method of

      logger.level = Logger::IMPORTANT      # or Capistrano::Logger::IMPORTANT

And then what does the before/after syntax look like compared to the integration example I give in the README.md

[jondavidjohn]

@leehambley Also, in the mailing list thread you mention that the pretty formatter is swappable. Could you point me in that direction if that seems like a cleaner point of integration.

[leehambley]

The Pretty formatter is here: https://github.com/leehambley/sshkit - it could be modified to accept other types of objects, or replaced with something less verbose (we prefer verbosity as it equals transparency for new users) - It's tested (not comprehensively, but it's there)

If you want to target leaner logging solutions to Cap it's worth noting according to the new DSL (http://capistranorb.com) anything in the on() block is evaluated inside of SSHKit's loaded backend, which means some glue code if you want parity inside and outside of on, but still with in task (we solved this wt a logging modeule injected into both places)

If you do hack something up, you'll be the first consumer of the new IO orientated printer strategy, so if there's any changes we can make to support you, feel free to let us know.

[jondavidjohn]

@leehambley

Looked in to this briefly, and if I understand you correctly Cap 3 output is generated from multiple places, even pieces that are outside of Capistrano? via SSHKit?

Seems like this would be difficult to customize.

You mentioned an IO oriented printer, is there a way to provide your own printer?

[leehambley]

Yes, just provide the class and provide it to SSJKit as the printer io On 15 Nov 2013 17:58, "Jonathan Johnson" [email protected] wrote:

@leehambley https://github.com/leehambley

Looked in to this briefly, and if I understand you correctly Cap 3 output is generated from multiple places, even pieces that are outside of Capistrano? via SSHKit?

Seems like this would be difficult to customize.

You mentioned an IO oriented printer, is there a way to provide your own printer?

— Reply to this email directly or view it on GitHubhttps://github.com/crowdfavorite/gem-steps/issues/9#issuecomment-28584820 .

[ddarbyson]

+1 for Cap3 compatibility

[Aupajo]

:+1:

[jeffbyrnes]

:+1:

[leehambley]

https://github.com/capistrano/sshkit/blob/master/EXAMPLES.md#implement-a-dirt-simple-formatter-class