Tutorial out of date

[baron0426]

Hello, I'm currently building a smart contract using go api from scratch and I'm reading this....
https://github.com/hyperledger/fabric-contract-api-go/blob/main/tutorials/getting-started.md
It involves a step where I need files from fabric-samples/chaincode-docker-devmode
but this folder doesn't exist in the latest fabric-samples.
Can someone please tell me the newest way to implement this?

[jt-nti]

Hi @baron0426, thanks for the issue. You should be able to use the Fabric Test Network instead. That's different in that you will need to package and install the chaincode instead of running it yourself. For a similar developer experience, you could try using chaincode as a server, which might the best option for updating the getting started guide when PR hyperledger/fabric-samples#560 gets merged. Hope that helps.

[ionicsolutions]

Just as a note: According to hyperledger/fabric-samples#314, the preferred way is to use https://github.com/hyperledger/fabric/blob/main/docs/source/peer-chaincode-devmode.md

However, it requires several adaptions and tweaking of parameters to work.

[mock123456]

Hope to update the tour !

[mbwhite]

thanks @mock123456 - just to clarify - are you saying you yourself would be able to update the tour?

PRs most welcome :-)

[shashank-priyadarshi]

Hi @mbwhite based on hyperledger/fabric-samples#314, sample has been removed. The documentation is outdated still. I would like to take this up, can you please suggest if a sample is required or just the README needs to be updated.

[bestbeforetoday]

From my perspective, a new sample is not required. Just an update to the tutorial.

The preferred approach to debug and do rapid development of smart contracts is to use chaincode as an external service. The asset-transfer-basic/chaincode-external sample demonstrates this and perhaps could be used if you need to refer to sample code.

The full-stack-asset-transfer-guide sample describes this approach and has a practical walk-through (using Node.js) in probably too much detail for this tutorial. There might be information there you can draw on for a tutorial update though.

If you'd like to work on an update to the tutorial in this repository, I can assign this issue to you.

[shashank-priyadarshi]

Yes I would like to take this up.