Table of Contents
This repository contains the services for the MECAnywhere project that are used to interact with pymeca and the smart contracts. Use the pymeca-actors to join the MECAnywhere ecosystem now!
Open https://sbip-sg.github.io/mecanywhere/ for online documentation + user guides.
- did-go
- Decentalized Identity (DID) service written in Golang
- example-tasks
- Example tasks for the MECAnywhere platform
- README to build tasks
- Pymeca actors
- Template actors that use pymeca library to interact with the smart contracts. These come in the form of CLI.
- README to setup
- User guides in docs
- Tower
- Hosted on the edge to provide task forwarding for end users
- README to setup
-
Configure keys/env variables (see Configuration -> Secret keys)
-
Pull submodules with
git submodule update --init --recursive
inpymeca
folder. -
Run docker services
docker compose up
to start all services as containers.docker compose up --build <service_name>
to rebuild a specific service.- +
-f docker-compose-internal.yaml
is for working with pymeca library changes. - +
-f docker-compose.yaml
is for working with pymeca version from pypi.
Options: manual, docker local (recommended), docker testnet
- For manual:
- Secret keys can be loaded in
.env
in each service folder. Follow the.env.example
file for the required variables.
- Secret keys can be loaded in
- For docker local/testnet:
- Secret keys are loaded by creating a
keys
folder in this base directory wherecompose.yaml
is. Each file contains the secret key and the file name is the name of the secret. Required variables are shown incompose.yaml
.- For python services, you have to add your variables in the settings class in
config.py
too.
- For python services, you have to add your variables in the settings class in
- Secret keys are loaded by creating a
Format: key: value
See compose files for the dependent services of each key.
tower_private_key.txt
: private key of the wallet/account for tower actor that calls the smart contracts