stack-orchestrator/stack_orchestrator/data/stacks/mobymask
Thomas E Lackey 937b983ec9
All checks were successful
Lint Checks / Run linter (push) Successful in 56s
Publish / Build and publish (push) Successful in 1m24s
Deploy Test / Run deploy test suite (push) Successful in 5m24s
Webapp Test / Run webapp test suite (push) Successful in 4m57s
Smoke Test / Run basic test suite (push) Successful in 4m48s
Update links from github.com to git.vdb.to (#732)
Update links and references to github.com to git.vdb.to.

Also enable the flake8 lint action in gitea.

Reviewed-on: #732
Co-authored-by: Thomas E Lackey <telackey@bozemanpass.com>
Co-committed-by: Thomas E Lackey <telackey@bozemanpass.com>
2024-02-06 22:42:44 +00:00
..
README.md Update links from github.com to git.vdb.to (#732) 2024-02-06 22:42:44 +00:00
stack.yml Rename app -> stack_orchestrator (#625) 2023-11-07 00:06:55 -07:00

MobyMask

The MobyMask watcher is a Laconic Network component that provides efficient access to MobyMask contract data from Ethereum, along with evidence allowing users to verify the correctness of that data. The watcher source code is available in this repository and a developer-oriented Docker Compose setup for the watcher can be found here. The watcher can be deployed automatically using the Laconic Stack Orchestrator tool as detailed below:

Deploy the MobyMask Watcher

The instructions below show how to deploy a MobyMask watcher using laconic-stack-orchestrator (the installation of which is covered here).

This deployment expects that ipld-eth-server's endpoints are available on the local machine at http://ipld-eth-server.example.com:8083/graphql and http://ipld-eth-server.example.com:8082. More advanced configurations are supported by modifying the watcher's config file.

Clone required repositories

$ laconic-so --stack mobymask setup-repositories

Build the watcher container

$ laconic-so --stack mobymask build-containers

This should create a container with tag cerc/watcher-mobymask in the local image registry.

Create a deployment

$ laconic-so --stack mobymask deploy init --output mobymask-spec.yml
$ laconic-so deploy create --spec-file mobymask-spec.yml --deployment-dir mobymask-deployment

External ipld-eth-server endpoint can be set in watcher config file in the deployment directory:

mobymask-deployment/config/watcher-mobymask/mobymask-watcher.toml

Start the stack

First the watcher database has to be initialized. Start only the mobymask-watcher-db service:

$ laconic-so deployment --dir mobymask-deployment start mobymask-watcher-db

Next find the container's id using docker ps then run the following command to initialize the database:

$ docker exec -i <mobymask-watcher-db-container> psql -U vdbm mobymask-watcher < mobymask-deployment/config/watcher-mobymask/mobymask-watcher-db.sql

Finally start the remaining containers:

$ laconic-so deployment --dir mobymask-deployment start

Correct operation should be verified by following the instructions here, checking GraphQL queries return valid results in the watcher's playground.

Clean up

Stop all the services running in background:

$ laconic-so deployment --dir mobymask-deployment stop

Data volumes

Container data volumes are bind-mounted to specified paths in the host filesystem. The default setup (generated by laconic-so deploy init) places the volumes in the ./data subdirectory of the deployment directory:

$ cat mobymask-spec.yml
stack: mobymask
ports:
  mobymask-watcher-db:
   - 0.0.0.0:15432:5432
  mobymask-watcher-job-runner:
   - 0.0.0.0:9000:9000
  mobymask-watcher-server:
   - 0.0.0.0:3001:3001
   - 0.0.0.0:9001:9001
volumes:
  mobymask_watcher_db_data: ./data/mobymask_watcher_db_data

The directory can be changed before laconic-so deploy create