forc-deploy
USAGE:
forc deploy [OPTIONS] [SIGNING_KEY]
ARGS:
<SIGNING_KEY> Set the key to be used for signing
OPTIONS:
--build-profile
<BUILD_PROFILE>
Build target for code generation. Name of the build profile to use. If it is not specified, forc will use debug build profile
-g
, --debug-outfile
<DEBUG_OUTFILE>
If set, outputs source file mapping in JSON format
--gas-limit
<GAS_LIMIT>
Set the transaction gas limit. Defaults to the maximum gas limit
--gas-price
<GAS_PRICE>
Set the transaction gas price. Defaults to 0
-h
, --help
Print help information
--locked
Requires that the Forc.lock file is up-to-date. If the lock file is missing, or it needs to be updated, Forc will exit with an error
--minify-json-abi
By default the JSON for ABIs is formatted for human readability. By using this option JSON output will be "minified", i.e. all on one line without whitespace
--minify-json-storage-slots
By default the JSON for initial storage slots is formatted for human readability. By using this option JSON output will be "minified", i.e. all on one line without whitespace
-o
<BINARY_OUTFILE>
If set, outputs a binary file representing the script bytes
--offline
Offline mode, prevents Forc from using the network when managing dependencies. Meaning it will only try to use previously downloaded dependencies
--output-directory
<OUTPUT_DIRECTORY>
The directory in which the sway compiler output artifacts are placed.
By default, this is <project-root>/out
.
-p
, --path
<PATH>
Path to the project, if not specified, current working directory will be used
--print-ast
Print the generated Sway AST (Abstract Syntax Tree)
--print-dca-graph
Print the computed DCA (Dead Code Analysis) graph
--print-finalized-asm
Print the finalized ASM.
This is the state of the ASM with registers allocated and optimisations applied.
--print-intermediate-asm
Print the generated ASM.
This is the state of the ASM prior to performing register allocation and other ASM optimisations.
--print-ir
Print the generated Sway IR (Intermediate Representation)
--release
Use release build plan. If a custom release plan is not specified, it is implicitly added to the manifest file.
If --build-profile is also provided, forc omits this flag and uses provided build-profile.
-t
, --terse
Terse mode. Limited warning and error output
--time-phases
Output the time elapsed over each part of the compilation process
-u
, --url
<URL>
The node url to deploy, if not specified uses DEFAULT_NODE_URL. If url is specified overrides network url in manifest file (if there is one)
--unsigned
Do not sign the transaction
-V
, --version
Print version information
EXAMPLE
You can use forc deploy
, which triggers a contract deployment transaction and sends it to a running node.
Alternatively, you can deploy your Sway contract programmatically using fuels-rs, our Rust SDK.
You can find an example within our fuels-rs book.