Avoid removing existing console deployment

This commit is contained in:
Prathamesh Musale 2025-06-13 18:57:11 +05:30
parent 6fe037b3a2
commit 5a608cd344

View File

@ -10,7 +10,7 @@ A Laconic mainnet node (see [run-validator.md](./run-validator.md))
```bash ```bash
# In directory where laconic-console deployment was created # In directory where laconic-console deployment was created
laconic-so deployment --dir laconic-console-deployment stop --delete-volumes laconic-so deployment --dir laconic-console-deployment stop
``` ```
* Stop webapp deployer: * Stop webapp deployer:
@ -23,17 +23,7 @@ A Laconic mainnet node (see [run-validator.md](./run-validator.md))
## Update laconic console ## Update laconic console
* Remove an existing console deployment: * Update the console config (`laconic-console-deployment/config.env`) if required:
```bash
# In directory where laconic-console deployment was created
# WARNING: Backup the config if required
rm -rf laconic-console-deployment
```
* Follow [laconic-console](https://git.vdb.to/cerc-io/testnet-laconicd-stack/src/branch/main/stack-orchestrator/stacks/laconic-console) stack instructions to setup a new laconic-console deployment
* Example configuration:
```bash ```bash
# CLI configuration # CLI configuration
@ -46,23 +36,25 @@ A Laconic mainnet node (see [run-validator.md](./run-validator.md))
CERC_LACONICD_CHAIN_ID=laconic-mainnet CERC_LACONICD_CHAIN_ID=laconic-mainnet
# your private key
CERC_LACONICD_USER_KEY=
# your bond id (optional)
CERC_LACONICD_BOND_ID=
# Gas price to use for txs (default: 0.001alnt)
# Use for auto fees calculation, gas and fees not required to be set in that case
# Reference: https://git.vdb.to/cerc-io/laconic-registry-cli#gas-and-fees
CERC_LACONICD_GASPRICE=
# Console configuration
# Laconicd (hosted) GQL endpoint (can be pointed to your node) # Laconicd (hosted) GQL endpoint (can be pointed to your node)
LACONIC_HOSTED_ENDPOINT=https://laconicd-mainnet.laconic.com LACONIC_HOSTED_ENDPOINT=https://laconicd-mainnet.laconic.com
``` ```
* Update any other config values as required
* Start the deployment:
```bash
laconic-so deployment --dir laconic-console-deployment start
```
* Use the cli service for any registry CLI operations:
```bash
# Example
laconic-so deployment --dir laconic-console-deployment exec cli "laconic registry status"
```
## Check authority and deployer record ## Check authority and deployer record
* The state has been carried over from SAPO testnet to the mainnet, if you had authority and records on the SAPO testnet, they should be present on mainnet as well * The state has been carried over from SAPO testnet to the mainnet, if you had authority and records on the SAPO testnet, they should be present on mainnet as well