cerc-io/stack-orchestrator
17
1
Fork 3
Code Issues 113 Pull Requests 18 Actions Packages Projects Releases 480 Wiki Activity

Update doc for fixturenet-laconic-loaded stack
All checks were successful
Lint Checks / Run linter (pull_request) Successful in 41s
Details
Webapp Test / Run webapp test suite (pull_request) Successful in 3m47s
Details
Deploy Test / Run deploy test suite (pull_request) Successful in 5m52s
Details
Smoke Test / Run basic test suite (pull_request) Successful in 5m51s
Details
K8s Deploy Test / Run deploy test suite on kind/k8s (pull_request) Successful in 9m39s
Details

Browse Source
This commit is contained in:
David Boreham 2024-02-21 10:29:15 -07:00
parent db4986dcc6
commit d4152b7ce3
1 changed files with 104 additions and 97 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
docs/laconicd-with-console.md
View File

@ -15,12 +15,11 @@ To avoid hiccups on Mac M1/M2 and any local machine nuances that may affect the
16 GB Memory / 8 Intel vCPUs / 160 GB Disk. 16 GB Memory / 8 Intel vCPUs / 160 GB Disk.
1. Login to the droplet as root (either by SSH key or password set in the DO console) 1. Login to the droplet as root (either by SSH key or password set in the DO console)
``` ```
ssh root@IP ssh root@IP
``` ```
2. Get the install script, give it executable permissions, and run it: 1. Get the install script, give it executable permissions, and run it:
``` ```
curl -o install.sh https://raw.githubusercontent.com/cerc-io/stack-orchestrator/main/scripts/quick-install-linux.sh curl -o install.sh https://raw.githubusercontent.com/cerc-io/stack-orchestrator/main/scripts/quick-install-linux.sh
@ -32,7 +31,7 @@ chmod +x install.sh
bash install.sh bash install.sh
``` ```
3. Confirm docker was installed and activate the changes in `~/.profile`: 1. Confirm docker was installed and activate the changes in `~/.profile`:
``` ```
docker run hello-world docker run hello-world
@ -41,7 +40,7 @@ docker run hello-world
source ~/.profile source ~/.profile
``` ```
4. Verify installation: 1. Verify installation:
``` ```
laconic-so version laconic-so version
@ -55,13 +54,7 @@ laconic-so version
laconic-so --stack fixturenet-laconic-loaded setup-repositories --include git.vdb.to/cerc-io/laconicd,git.vdb.to/cerc-io/laconic-sdk,git.vdb.to/cerc-io/laconic-registry-cli,git.vdb.to/cerc-io/laconic-console laconic-so --stack fixturenet-laconic-loaded setup-repositories --include git.vdb.to/cerc-io/laconicd,git.vdb.to/cerc-io/laconic-sdk,git.vdb.to/cerc-io/laconic-registry-cli,git.vdb.to/cerc-io/laconic-console
``` ```
2. Set this environment variable to the Laconic self-hosted Gitea instance: 1. Build the containers:
```
export CERC_NPM_REGISTRY_URL=https://git.vdb.to/api/packages/cerc-io/npm/
```
3. Build the containers:
``` ```
laconic-so --stack fixturenet-laconic-loaded build-containers laconic-so --stack fixturenet-laconic-loaded build-containers
@ -69,22 +62,34 @@ laconic-so --stack fixturenet-laconic-loaded build-containers
It's possible to run into an `ESOCKETTIMEDOUT` error, e.g., `error An unexpected error occurred: "https://registry.yarnpkg.com/@material-ui/icons/-/icons-4.11.3.tgz: ESOCKETTIMEDOUT"`. This may happen even if you have a great internet connection. In that case, re-run the `build-containers` command. It's possible to run into an `ESOCKETTIMEDOUT` error, e.g., `error An unexpected error occurred: "https://registry.yarnpkg.com/@material-ui/icons/-/icons-4.11.3.tgz: ESOCKETTIMEDOUT"`. This may happen even if you have a great internet connection. In that case, re-run the `build-containers` command.
4. Set this environment variable to your droplet's IP address:
1. Set this environment variable to your droplet's IP address or fully qualified DNS host name if it has one:
``` ```
export LACONIC_HOSTED_ENDPOINT=http://<your-IP> export BACKEND_ENDPOINT=http://<your-IP-or-hostname>:9473
```
e.g.
```
export BACKEND_ENDPOINT=http://my-test-server.example.com:9473
``` ```
5. Deploy the stack: 1. Create a deployment directory for the stack:
```
laconic-so --stack fixturenet-laconic-loaded deploy init --output laconic-loaded.spec --map-ports-to-host any-same --config LACONIC_HOSTED_ENDPOINT=$BACKEND_ENDPOINT
```
```
laconic-so --stack fixturenet-laconic-loaded deploy create --deployment-dir laconic-loaded-deployment --spec-file laconic-loaded.spec
```
2. Start the stack:
``` ```
laconic-so --stack fixturenet-laconic-loaded deploy up laconic-so deployment --dir laconic-loaded-deployment start
``` ```
6. Check the logs: 3. Check the logs:
``` ```
laconic-so --stack fixturenet-laconic-loaded deploy logs laconic-so deployment --dir laconic-loaded-deployment logs
``` ```
You'll see output from `laconicd` and the block height should be >1 to confirm it is running: You'll see output from `laconicd` and the block height should be >1 to confirm it is running:
@ -102,10 +107,10 @@ laconic-5cd0a80c1442c3044c8b295d26426bae-laconicd-1 | 9:30PM INF committ
laconic-5cd0a80c1442c3044c8b295d26426bae-laconicd-1 | 9:30PM INF indexed block exents height=13 module=txindex server=node laconic-5cd0a80c1442c3044c8b295d26426bae-laconicd-1 | 9:30PM INF indexed block exents height=13 module=txindex server=node
``` ```
7. Confirm operation of the registry CLI: 4. Confirm operation of the registry CLI:
``` ```
laconic-so --stack fixturenet-laconic-loaded deploy exec cli "laconic cns status" laconic-so deployment --dir laconic-loaded-deployment exec cli "laconic cns status"
``` ```
``` ```
@ -141,6 +146,8 @@ laconic-so --stack fixturenet-laconic-loaded deploy exec cli "laconic cns status
## Configure Digital Ocean firewall ## Configure Digital Ocean firewall
(Note this step may not be necessary depending on the droplet image used)
Let's open some ports. Let's open some ports.
1. In the Digital Ocean web console, navigate to your droplet's main page. Select the "Networking" tab and scroll down to "Firewall". 1. In the Digital Ocean web console, navigate to your droplet's main page. Select the "Networking" tab and scroll down to "Firewall".