fabric-samples/full-stack-asset-transfer-guide/applications/rest-api
Mark S. Lewis b931df3a5f Explicitly specify hash in client applications
For some signing implementations, such as ed25519, a non-default hash
implementation must be specified when creating the Gateway connection in
client applications. Rather than relying on the default hash algorithm,
it is probably good practice in general to specify an algorithm that is
compatible with your signing implementation.

This change explicitly specifies the hash algorithm to raise visibility
of the option to select the hash algorithm.

Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
2024-10-07 12:25:40 -04:00
..
src Explicitly specify hash in client applications 2024-10-07 12:25:40 -04:00
.gitignore Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
asset-transfer.postman_collection.json Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
deployment.yaml Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
Dockerfile Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
LICENSE Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
package.json Update applications to use fabric-gateway v1.6.0 2024-09-25 13:18:45 +09:00
README.md Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
renovate.json Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852) 2022-11-10 10:40:27 -05:00
tsconfig.json Use fabric-gateway v1.4 2023-10-25 17:30:29 +09:00

Make sure all the certificates are generated as per the documentation in the below link https://github.com/hyperledgendary/full-stack-asset-transfer-guide/blob/main/docs/CloudReady/40-bananas.md

#Local development

npm install npm run prod

Import the postman collections and test the apis

#Kubernetes development

Step-1 Build docker image & Tag

docker build -t localhost:5000/rest-api .

Step-2 Push docker image to local registary

docker push localhost:5000/rest-api

Step-3 Create secrets for the certicates

kubectl create secret generic client-secret --from-file=keyPath=/home/ramdisk/my-full-stack/infrastructure/sample-network/temp/enrollments/org1/users/org1user/msp/keystore/key.pem --from-file=certPath=/home/ramdisk/my-full-stack/infrastructure/sample-network/temp/enrollments/org1/users/org1user/msp/signcerts/cert.pem --from-file=tlsCertPath=/home/ramdisk/my-full-stack/infrastructure/sample-network/temp/channel-msp/peerOrganizations/org1/msp/tlscacerts/tlsca-signcert.pem -n test-network

please replace the path of /home/ramdisk/my-full-stack/infrastructure/sample-network/temp with your system path

Step-4 Deploy the pods to k8s

kubectl apply -f deployment.yaml -n test-network

Step-5 Testing API's

Import the apis into postman and test the apis

create & list apis are tested.reminaing apis need be implemented