mesg-foundation / engine Goto Github PK

• create docker service (container)
• stop docker service (container)
• create stack (swarm or kubernetes)

• User
• Developer
• Runner

Update the workflow commands according to the documentation.

To summarize shortly: the marketplace workflow commands have been merged with workflow.

This is needed when testing and deploying a service

Update the service commands according to the documentation.

To summarize shortly: the marketplace service commands have been merged with service.

• Executors
• Validators

When the docker is not started, I get this ugly error:

Post http://unix.sock/services/create?: dial unix /var/run/docker.sock: connect: no such file or directory.

We should add a nice message that say to start docker and give a link to docker website to install it in case the user didn't install it yet.

• Slack notifications
• Slack command

• Ethereum functions (database)
• Services
• Workflows

• write to a collection

• Address generation #60
• Store address and private key in a secure way #61
• Backup #62
• Sign transaction #63

My docker was not a swarm manager. I had to enter a command manually. I get this error: API error (503): This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.. So I run the command docker swarm init. Can we run this command automatically?

• Javascript functions

Have a way through the CLI to execute a local service in development

With docker we need to make sure that the service will only be able to access the mesg application and not any other services

1 registration per service per node

Stake as amount of MESG and a period of time

• state (inputs + results)
• list of tasks
• list of executions
• statistics

• Send with Sendgrid
• Receive with Sendgrid

Deploy a very simple ethereum testnet.
Can use Puppeth.

Update the account commands with the doc.

• Account
• Service
• Workflow

• Receive webhook request
• Send webhook request

Goal

• Be able to be notified when we listen for an event only if it's a specific event, by default we should listen every events
• Be able to listen a specific output from a specific task, by default we listen all the outputs of all the tasks

Accessible from CLI

• Try to use a super light version of the ethereum client. We only need to listen for transactions, no history. (--sync=light)
• Send signed transaction
• Send transaction
• Listen for blocks
• Listen fro contract events
• Encode event ABI to be able to filter it from the listener
• Decode event
• Call contract
• MESG Transfer implementation

We now enforce that a service has its own folder with a mandatory mesg.yml. See documentation.

All commands that require a service file, should now:

• look in the current folder for a mesg.yml file.
• accept a optional path the to service folder. EG: mesg-cli service validate ./PATH_TO_SERVICE_FOLDER

When deploying or starting a service file we need to verify that the format is valid.

JSON Schema is a good way to do that