Can we make roco asynchronous and api friendly?

[qfox]

A lot of existsSync, readFileSync, readDirSync calls exists at the moment.
process.exit buried deep in code — it should be moved out to bin/roco imho.
https://github.com/1602/roco/blob/master/lib/rockout.js#L300

I'm really like how it looks but need async and more configs, e.g. pass writable streams to catch remote output, make a prefix with time, disable (or overwrite) string colorize methods, etc.
Can we do something with it?

[1602]

It's a command line tool for deploying. It should be as simple as possible, imho.

[qfox]

Sure it's command line but why not to expose api? Btw async execution will allow to run commands synchronously on several hosts at the same moment. Especially it will be useful when execution takes a lot of time. Tests, builds, etc.

[qfox]

Okay, seems like capistrano have almost the same behaviour. So probably you're totally right.
But anyway I need almost the same functionality which roco have so I will try split up deploy library and command line caller. If you want to clean up roco I can try to make a version of roco on it.

[1602]

Carry on :)

[qfox]

Sorry for delay. I'm stuck in tests month ago and just want now to publish some work I've done on it.

[qfox]

@randunel please also take a look if you are interested in roco.

[randunel]

Well, it seems to me you're looking for capistrano indeed. I believe roco uses synchronous calls because it started as a fast/easy prototype, and this project is still in prototype stage, in spite of its age.

If you need writable streams, you might find adding ssh2 to roco useful and reusing its connections, instead of spawning a new ssh process for every command.