Stately doesn't handle new servers well

[stavfx]

When trying to clone from a server whose fingerprint has been already approved, stately asks to approved it once per every repo in the list and even then it doesn't look like it's working.
Our solution now is to "git clone" any random project from the server just to have git prompt to save that fingerprint and then run stately as usual.

Is it possible to have stately handle new fingerprints better?

[srgrn]

It's becouse the threads it opens for doing the clone each run separately.
I need to think there is proably a better way.
On Jan 21, 2015 11:35 AM, "stavfx" notifications@github.com wrote:

When trying to clone from a server whose fingerprint has been already
approved, stately asks to approved it once per every repo in the list and
even then it doesn't look like it's working.
Our solution now is to "git clone" any random project from the server just
to have git prompt to save that fingerprint and then run stately as usual.

Is it possible to have stately handle new fingerprints better?

—
Reply to this email directly or view it on GitHub
#4.

[stavfx]

maybe iterate over the servers before starting the "cloning threads" ?

[srgrn]

Could be I need to test
On Jan 21, 2015 11:39 AM, "stavfx" notifications@github.com wrote:

maybe iterate over the servers before starting the "cloning threads" ?

—
Reply to this email directly or view it on GitHub
#4 (comment).