@binod - Please use caution! When you locally build a version of the CHT you plan to deploy to production, you are creating a soft fork. Your fork will need to continually have future CHT Core releases merged to your branch and then continually build images. While this may be totally reasonable for your deployment, I just wanted to be sure to call this out.
Otherwise, to deploy a custom version of the CHT you would build images using the local-images call. Assuming your development environment is fully setup, your code is working locally, you would call:
npm ci
npm run build-dev
npm run local-images
And then to see the images you just built, you can list images and specify the branch name. Here’s my mrjones-test branch images I just built for example:
docker images --filter=reference='*/*:mrjones-test'
REPOSITORY TAG IMAGE ID CREATED SIZE
medicmobile/cht-couchdb mrjones-test 0359718bd2d7 5 minutes ago 285MB
medicmobile/cht-sentinel mrjones-test 7336bd54571b 5 minutes ago 508MB
medicmobile/cht-nginx mrjones-test 9953964f5efc 2 weeks ago 49.7MB
medicmobile/cht-haproxy-healthcheck mrjones-test 485cbf077f88 2 weeks ago 60.8MB
medicmobile/cht-haproxy mrjones-test d52c8d4cf8ee 2 weeks ago 487MB
you would then update your compose files to reference these images. You may find this forum thread helpful as well.