From ff4060e5cc29ab0e827301c30219861b6dd057ca Mon Sep 17 00:00:00 2001 From: Prathamesh Musale Date: Tue, 26 Nov 2024 18:26:46 +0530 Subject: [PATCH] Add a step to update deployer compose file --- service-provider.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/service-provider.md b/service-provider.md index bb7ab0b..a2792c0 100644 --- a/service-provider.md +++ b/service-provider.md @@ -236,6 +236,13 @@ Follow the steps below to point your deployer to the SAPO testnet laconic-so deployment --dir webapp-deployer push-images ``` +* Overwrite an existing compose file with the latest one: + + ```bash + # In directory where webapp-deployer deployment folder exists + cp ~/cerc/webapp-deployment-status-api/docker-compose.yml webapp-deployer/compose/docker-compose-webapp-deployer-backend.yml + ``` + * Update deployer laconic registry config (`webapp-deployer/data/config/laconic.yml`) with new endpoints: ```bash @@ -249,7 +256,9 @@ Follow the steps below to point your deployer to the SAPO testnet gasPrice: 0.001alnt ``` - Note: Existing `userKey` and `bondId` can be used since they are carried over from laconicd stage1 to testnet2 + Note: + * Your SAPO testnet node endpoints can be used for `rpcEndpoint` and `gqlEndpoint` + * Existing `userKey` and `bondId` can be used since they are carried over from laconicd stage1 to testnet2 * Publish a new webapp deployer record: