Canton -c some.config vs daml canton-console
Hi there, I’m trying to figure out the differences between
- the canton console after started domain using canton -c some.config
- connect to an existing domain using daml canton-console.
And also what parameters do we need to use daml canton-console to access existing domain? its args have host address and port, domain admin address and port. How can we add authentication to the domain admin port.
daml canton-console is really just the canton console preconfigured to connect to the sandbox started via daml sandbox. If you’re not working with Sandbox, I recommend to just use Canton directly. To connect to a Canton process remotely (which is how daml canton-console operates) take a look at the corresponding docs.
What about in the production-like scenario? e.g. Canton is setup to run as daemon and domain administrator need to carry out operation tasks like managing participants?
In production, you can create a config file with a remote participant and then start Canton locally to connect to your daemon. That’s what the docs I linked above describe.