Update Watcher deployment instructions#11
Conversation
Documentation on how to configure an Ergo Watcher instance
Update and refine Cardano Watcher instructions
Update and refine Ergo configuration instructions
|
Great updates! I'll also note, we should add best practice approach to running multiple watchers. That is if I'm running ergo, what's the easiest recommended steps to setup a cardano watcher. I've noticed the best approach is to within the ~/rosenbridge/operation/ directory, Then proceed to follow setup steps. If you do the following: you'll run the same docker compose service as the ergo watcher and it will be essentially a duplicate. You need the watcher directory to have a different name. |
|
Another addition suggestion, how to setup bitcoin watcher config from a remote machine running the full node. The url should probably include a hint to also include the port number, like the ergo node has http://10.0.X.YYY:9053 So should the bitcoin local.yaml config include at least in the comments a hint to include the port number. E.g. |
|
Bumping this MR for an update. |
I've performed an overhaul of Watcher deploy-docker.md instructions and created steps that are needed to be taken to help guide some not so technical users through the process:
Following on from the 2.0 release and as these are Docker specific, I've set instructions to have API Key and mnemonic to live in the .env file as a requirement.
Also to not get confusing as more networks are added, I've disconnected the docker deployment instruction and network configuration instructions. Networks have separate, (linked to from deploy-docker.md) -config.md with network specific yaml and .env instructions/examples.
Tidied and updated the example .env and yaml's with current recommended settings.
Added links to list of available indexed nodes, and wallets