-
Notifications
You must be signed in to change notification settings - Fork 285
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
docs(examples): increase supply chain image boot responsiveness #780 #1152
Conversation
…ledger-cacti#780 Added logging to all 3 of the test ledger classes that are being used which are taking up most of the boot time. Now users can see the setup process as it chugs along step by step and in general be much more confident while waiting that things are indeed happening instead of the container just being in a zombie state. Also added an additional point in the README.md file claryfying that one needs to have a working installation of docker on their machine. Decided to not go into any more detail than that because the (linked) docker for desktop documentation is the best/most robust resrouces available there is and it would be hard to compete with it if we were to produce our own installation instructions. Fixes hyperledger-cacti#780 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Codecov Report
@@ Coverage Diff @@
## main #1152 +/- ##
==========================================
+ Coverage 73.18% 73.20% +0.02%
==========================================
Files 248 248
Lines 8744 8768 +24
Branches 1018 1023 +5
==========================================
+ Hits 6399 6419 +20
Misses 1796 1796
- Partials 549 553 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added logging to all 3 of the test ledger classes that are being used
which are taking up most of the boot time.
Now users can see the setup process as it chugs along step by step and
in general be much more confident while waiting that things are indeed
happening instead of the container just being in a zombie state.
Also added an additional point in the README.md file claryfying that
one needs to have a working installation of docker on their machine.
Decided to not go into any more detail than that because the (linked)
docker for desktop documentation is the best/most robust resrouces
available there is and it would be hard to compete with it if we were
to produce our own installation instructions.
Fixes #780
Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com