Markus Korn

@tobami, any idea on that one?

the problem here is that - if we only change this environment variable to True - we won't really implement a `skip_failures` feature, it is just a `skip_on_connection_error` but not...

As a side note: I don't think simply catching the fabric error and resuming with the next node is an option. Because skipping nodes programmatically is not a good idea...

Maybe a more generic solution is the way to go: - add a new command `node_from_file:` which reads hostnames from a given file and deploys them. Format of this file...

just as a side note for everyone who is using fakes3 in docker, and does not want to (or cannot) use the `-H ` "workaround": the solution is to link...