Add juvix dev anoma {start, stop, status}
to manage an Anoma client
#3183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
juvix dev anoma {start, stop, status}
commands tomanage a running Anoma client.
The motivation for this is that we can add additional commands (e.g
indexer
,prove
,(mempool)-submit
) which interact with thepersistent Anoma client.
juvix dev anoma start
now writes a configuration file in<juvix_config>/anoma-client/config.yaml
which contains the host URL andport of the started Anoma client and the pid of the Anoma client process.
For example:
config.yaml
The
anoma stop
command kills the Anoma client and theanoma status
command shows the config of the currently running client.
There can be at most one Anoma client running when using this mechanism.
Dependency
This PR adds a new dependency on the
unix
package. This is used for APIs to send signals to processes.CLI docs
juvix dev anoma
juvix dev anoma start
juvix dev anoma status
juvix dev anoma stop