.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
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:
-sallows you to provide your secret key (sk) in base64
-aallows you to specify a relay in multiaddr format, e.g.,
aqua config default_peers <krasnodar, testnet, stage>command enumerates you the respective network multiaddresses of available Fluence nodes.
-dallows you to specify data arguments as a json map:
pallows you to specify data arguments, see
--data, as a file. Note that
--data-pathare mutually exclusive.
-jallows you to describe a service that will return a JSON. This service must be described in Aqua. There can be multiple functions strictly without any arguments. Also, you can use this flag multiple times targeting multiple services in different files. There is an example of a service description in Aqua and JSON:
aqua run --helpfor a complete listing of available flags and explanations.
aqua key createutility allows you to create an ed25519-based keypair in base64:
aqua config default_peersutility shows a list of peers in multiaddr format for a specific Fluence network. Currently, there are three environments:
krasnodar, the default network,