Skip to Content
Product GuideRun operator commands

Run operator commands

A command typed straight into your shell cannot reach the installation’s database or meshMeshA set of connected Mycelium services that exchange updates and keep the NovusLens log.. Run it with ./lens, which runs it inside the installation’s reasoning service.

  1. Open a terminal in the installation directory, the one that holds .novuslens.env. To run from elsewhere, add --directory <path> or set NOVUSLENS_INSTALL_DIR.
  2. Check that the installation is running: ./lens status. If it is stopped, run ./lens resume.
  3. Run the command through ./lens. For example, print the flags of the command that creates an account:
./lens graph create-viewer --help
  1. Where a command asks for --viewer, give the operator login you created during setup.

./lens reads only --directory and --version as its own options (exec also takes --service). Put them after graph or connectors and before the verb. Everything after the verb belongs to the command, and --org is an ordinary flag after the verb.

Give a command a file

A file named by --file, --mapping, --fixture or --enrolment is copied from your host into the service first. A host path named by --out is copied back after the command succeeds.

./lens connectors agent-source enrol --org <org> ... --out product-source.json
./lens connectors agent-source activate --org <org> --viewer <operator-login> --enrolment product-source.json

Keep these files outside /tmp. Inside the service, a /tmp path names the service’s own file. For any other file option, send the file on standard input, then give that path:

./lens exec -- sh -c 'cat > /tmp/input.json' < input.json

Reach the mesh

./lens graph materialise and ./lens graph requeue need --host mesh-0. So does ./lens exec -- python -m conway_mesh.build. ./lens graph keyperson reads the installation’s configured mesh address and needs no --host.

Next steps

Read more

Last updated
Subscribe to notificationsKeep the secrets