-
Notifications
You must be signed in to change notification settings - Fork 516
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
Allow demo scripts to run outside of Docker; add command line parsing #84
Allow demo scripts to run outside of Docker; add command line parsing #84
Conversation
Codecov Report
@@ Coverage Diff @@
## master #84 +/- ##
=======================================
Coverage 70.98% 70.98%
=======================================
Files 177 177
Lines 7524 7524
=======================================
Hits 5341 5341
Misses 2183 2183 |
For native Python run with |
#(schema_id, credential_definition_id) = await agent.register_schema_and_creddef( | ||
# "employee id schema", version, ["employee_id", "name", "date", "position"] | ||
# ) | ||
# version = format( |
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.
Are these comments safe to delete?
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.
@ianco ?
…ng; detect missing indy library early Signed-off-by: Andrew Whitehead <[email protected]>
Signed-off-by: Andrew Whitehead <[email protected]>
Signed-off-by: Andrew Whitehead <[email protected]>
b9c3b75
to
9c5835f
Compare
@andrewwhitehead the instructions are not updated (and presumably I still need to run the When I do run it using python, I get an python3-indy module not installed error message. I assume we need a pointer to somewhere in indy-sdk land for how to build the indy module and put it into our instructions. I'd say we go with this and I'll add a line that says "You have to build indy-sdk However, even if we do that, we still won't have it working, because Sam has fixed this issue (the folders) but is speculating that the startup parameters are not right. Don't know if that is correct... Perhaps that fastest thing we can do is get on a session with Sam to figure out why it is not working on his system and thus, with python generally? Any volunteers? |
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.
Worked locally.
Running local ledger from the indy-sdk:
docker run -itd -p 9701-9708:9701-9708 indy_pool
Running local postgres:
docker run --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -d -p 5432:5432 postgres -c 'log_statement=all' -c 'logging_collector=on' -c 'log_destination=stderr'
Running local ledger browser from von-network:
GENESIS_FILE=/path/to/local-genesis.txt PORT=9000 REGISTER_NEW_DIDS=true python -m server.server
... and then ran the faber and alice roles from the demo directory:
python3 -m runners.faber --port 8020
python3 -m runners.alice --port 8030
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.
@ianco verified running on plain python. I verified running with Docker and Docker.
…/credential-attachments-verifier Validate supplements upon proof request
No description provided.