Skip to content
This repository has been archived by the owner on Mar 8, 2020. It is now read-only.

Properly explain what is "getting-started" in main README and correct 'info.js' instruction #81

Merged
merged 2 commits into from Aug 17, 2017

Conversation

mahoney1
Copy link
Contributor

@mahoney1 mahoney1 commented Aug 16, 2017

Explain that Digital Property app is the 'getting-started' app and correctly explain the instruction for 'info.js' as being in the 'main sample-applications' README file, where previously it was only explained deep in the README for digitalproperty-app. Still described there too - but as an OPTIONAL step, if someone had come 'straight' to that sample app directory, directly and was following the instructions on cloning the sample-applications repository.

This PR relates to https://github.com/hyperledger/composer-sample-applications/issues/72 and also https://github.com/hyperledger/composer-sample-applications/issues/78 following 'tidy-up' of 0.6 instructions.

Paul O'M added 2 commits August 16, 2017 17:23
If a user comes straight to the Digital Property app and runs, what is, an OPTIONAL step to see info about all the Sample Applications in the repo, then npm install must be run (at sample-applications level) before running the 'node info.js' step. Put in the word OPTIONAL, because they user can skip the step and go straight to deploying the sample digital property app. Also, the node info steps should be added back to the main README for sample-applications (will do so next)
Added that Digital Property app is the 'getting-started' app (otherwise not that clear) and also add in the 'info.js'  instruction which was buried in digitalproperty-app previously (but belongs here)
@nklincoln nklincoln merged commit be39bd9 into hyperledger-archives:master Aug 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
2 participants