It was really pleasing this morning to see the network function end to end. Client was using the mock routing framework to test its functionality of self-auth and rest-api. Routing and Vaults were separately tested and were functional. Now with client, vaults, routing and other crates all actually integrated, there were some unavoidable but only a few changes in some of them related to interfacing with each other. Once that was out of the way (we finished it yesterday with some of us stretching into late evenings too) and a couple of PR’s merged just a few hours back, the whole network could be locally run and we could see the network wonderfully do what it is supposed to do . Of-course this is just the 2nd sprint and we have a demo-able product. It does have a lot of print-outs for us to see and test what is happening so the CLI menus sometimes get shadowed by these debug printouts but those are just the matter of beautification and will require a PR or two from here and there to remove those.
So just grab the latest master of client and vaults and then the following:
<1> run at-least 3 vault nodes (in 3 different terminals). The first vault node must be run as
cargo run --release -- --first
and the others (after the 1st one has begun) simply with
cargo run --release
<2> in yet another terminal run client:
cargo run --example rest_api --features "USE_ACTUAL_ROUTING"
cargo run --example self_authentication --features "USE_ACTUAL_ROUTING"
whichever one you please.
<a> Right now the login will seem to hang. Be patient and wait for 10 seconds or so. This is just a temporary thingy to allow enough time for bootstrapping phase to succeed.
<b> The CLI menus might get lost among lot of Debug messages. Needless to say - this is temporary too and just requires to turn off the print outs, not a very critical issue to address as present.
<c> delete the
maidsafe_vault.bootstrap.cache file from vault directory root time to time, this will reduce some printouts.
Relax and enjoy the network