-
Notifications
You must be signed in to change notification settings - Fork 11
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
Can we make roco asynchronous and api friendly? #8
Comments
It's a command line tool for deploying. It should be as simple as possible, imho. |
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. |
Okay, seems like capistrano have almost the same behaviour. So probably you're totally right. |
Carry on :) |
Sorry for delay. I'm stuck in tests month ago and just want now to publish some work I've done on it. |
@randunel please also take a look if you are interested in roco. |
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 |
A lot of
existsSync
,readFileSync
,readDirSync
calls exists at the moment.process.exit
buried deep in code — it should be moved out tobin/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?
The text was updated successfully, but these errors were encountered: