.aquafiles from the specified input directory, e.g.,
src/generated. Please note that if the specified output directory does not exist, the CLI creates it for you:
.d.tsTypeScript files by default. Output files will contain functions exported from
.aquafiles and methods for registering defined services. You can read more about calling functions and service registration in the FluenceJS documentation.
--jsflag, which generates only
-aflag, which generates pure AIR code
--scheduled, which generates AIR code suitable for [script storage](add link)
aqua --helpfor a complete listing of available flags, subcommands and explanations.
aqua runcommand creates a one-shot client peer over the compiled Aqua code specified allowing you to quickly and effectively test Aqua code against deployed services on the network.
aqua runcommand provides additional features such as:
-s, which allows you to provide your secret key (sk) in base64
-a, which allows you to specify a relay in multiaddr format, e.g., /dns4/kras-04.fluence.dev/tcp/19001/wss/p2p/12D3KooWFEwNWcHqi9rtsmDhsYcDbRUCDXH84RC4FW6UfsFWaoHi
-d, which allows you to specify data arguments as a json map:
p, which allows you to specify data arguments, see
--data, as a file. Note that
--data-pathare mutually exclusive
aqua run --helpfor a complete listing of available flags and explanations.
aqua create_keypairutility allows you to create an ed25519-based keypair in base64: