undefined | Better HN

0 pointsgoosemo15y ago0 comments

The branch actually does client side forks, one for each server in a task. Then each call inside a task is run sequentially, as expected in normal fabric usage. I've also included the ability to set a pool size, so that one can manage the number of ssh connections open simultaneously.

0 comments

2 comments · 1 top-level

enki15y ago· 1 in thread

ah - so what you are doing speeds up deploys to multiple servers, while what i'm doing is meant to speed up an individual deploy.

i mostly just got tired of waiting for an individual deploy to my staging server.

btw thanks for emailing me! - i'll definitely look at your branch and see if i can help! (wasn't aware of it until today)

goosemoOP15y ago

Yeah, thats the goal anyways. I tend to reach out to 50+ servers at a time, and iterating though that on any tasks that take over a min is mind numbing.

Well through this post perhaps the branch will be better known, but I haven't really posted much about it in that I though it'd be done sooner. Then any mention of a branch would be negated by it's inclusion in master.

j / k navigate · click thread line to collapse