Thomas E Lackey
d2442bcc9b
Some checks failed
Fixturenet-Eth-Plugeth-Arm-Test / Run an Ethereum plugeth fixturenet test (push) Failing after 2s
Fixturenet-Eth-Plugeth-Test / Run an Ethereum plugeth fixturenet test (push) Failing after 56m21s
K8s Deploy Test / Run deploy test suite on kind/k8s (push) Successful in 8m53s
Database Test / Run database hosting test on kind/k8s (push) Successful in 11m3s
Container Registry Test / Run contaier registry hosting test on kind/k8s (push) Successful in 4m15s
Lint Checks / Run linter (push) Successful in 37s
Publish / Build and publish (push) Successful in 1m7s
Webapp Test / Run webapp test suite (push) Successful in 4m58s
Deploy Test / Run deploy test suite (push) Successful in 5m38s
Smoke Test / Run basic test suite (push) Successful in 5m0s
Fixturenet-Laconicd-Test / Run an Laconicd fixturenet test (push) Successful in 10m5s
revert Blind commit to fix laconic CLI calls after rename. (#784) `laconic cns` got renamed to `laconic registry` which breaks all the scripts and commands that use it. Reviewed-on: #784 Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com> Co-committed-by: Thomas E Lackey <telackey@bozemanpass.com> Reviewed-on: #788 |
||
|---|---|---|
| .. | ||
| README.md | ||
| stack.yml | ||
Laconic Fixturenet (experimental)
Testing a "Loaded" fixturenet with console.
Instructions for deploying a local Laconic blockchain "fixturenet" for development and testing purposes using laconic-stack-orchestrator.
Note: For building some NPMs, access to the @lirewine repositories is required. If you don't have access, see this tutorial to run this stack
1. Install Laconic Stack Orchestrator
Installation is covered in detail here but if you're on Linux and already have docker installed it should be as simple as:
$ mkdir my-working-dir
$ cd my-working-dir
$ curl -L -o ./laconic-so https://git.vdb.to/cerc-io/stack-orchestrator/releases/download/latest/laconic-so
$ chmod +x ./laconic-so
$ export PATH=$PATH:$(pwd) # Or move laconic-so to ~/bin or your favorite on-path directory
2. Prepare the local build environment
Note that this step needs only to be done once on a new machine. Detailed instructions can be found here. For the impatient run these commands:
$ laconic-so --stack build-support build-containers --exclude cerc/builder-gerbil
$ laconic-so --stack package-registry setup-repositories
$ laconic-so --stack package-registry build-containers
$ laconic-so --stack package-registry deploy-system up
Then add the localhost alias gitea.local and set CERC_NPM_AUTH_TOKEN to the token printed when the package-registry stack was deployed above:
$ sudo vi /etc/hosts
$ export CERC_NPM_AUTH_TOKEN=<my-token>
3. Clone required repositories
$ laconic-so --stack fixturenet-laconic-loaded setup-repositories
4. Build the stack's packages and containers
$ laconic-so --stack fixturenet-laconic-loaded build-npms
$ laconic-so --stack fixturenet-laconic-loaded build-containers
5. Deploy the stack
$ laconic-so --stack fixturenet-laconic-loaded deploy up
Correct operation should be verified by checking the laconicd container's logs with:
$ laconic-so --stack fixturenet-laconic-loaded deploy logs
6. Test with the Registry CLI
$ laconic-so --stack fixturenet-laconic-loaded deploy exec cli "laconic cns status"
7. View the laconic console
Get the URL for the console web app with this command (the port number will be different for each deployment):
$ echo http://localhost:$(laconic-so --stack fixturenet-laconic-loaded deploy port laconic-console 80 | cut -d ':' -f 2)
http://localhost:58364
Open that address with a browser. The console should display
8. Load demo data into the registry
$ laconic-so --stack fixturenet-laconic-loaded deploy exec cli ./scripts/create-demo-records.sh
Balance is: 99998999999999998999600000
Created bond with id: dd88e8d6f9567b32b28e70552aea4419c5dd3307ebae85a284d1fe38904e301a
Published demo-record-1.yml with id: bafyreierh3xnfivexlscdwubvczmddsnf46uytyfvrbdhkjzztvsz6ruly
The published record should be visible in the console.