Deploying to a generic DAML ledger¶
DAML ledgers expose a unified administration API. This means that deploying to a DAML ledger is no different from deploying to your local sandbox.
To deploy to a DAML ledger, run the following command from within your DAML project:
$ daml deploy --host=<HOST> --port=<PORT> --access-token-file=<TOKEN-FILE>
<PORT> is the hostname and port your ledger is listening on, which defaults
<TOKEN-FILE> is needed if your sandbox runs with authentication and needs to contain a JWT token with an
admin claim. If your sandbox is not
setup to use any authentication it can be omitted.
Instead of passing
--port flags to the command above, you can add the following
section to the project’s
ledger: host: <HOSTNAME> port: <PORT>
daml deploy command will
- upload the project’s compiled DAR file to the ledger. This will make the DAML templates defined in the current project available to the API users of the sandbox.
- allocate the parties specified in the project’s
daml.yamlon the ledger if they are missing.
For more further interactions with the ledger, use the
daml ledger command. Try running
ledger --help to get a list of available ledger commands:
$ daml ledger --help Usage: daml ledger COMMAND Interact with a remote DAML ledger. You can specify the ledger in daml.yaml with the ledger.host and ledger.port options, or you can pass the --host and --port flags to each command below. If the ledger is authenticated, you should pass the name of the file containing the token using the --access-token-file flag. Available options: -h,--help Show this help text Available commands: list-parties List parties known to ledger allocate-parties Allocate parties on ledger upload-dar Upload DAR file to ledger navigator Launch Navigator on ledger