Skip to content

Update Watcher deployment instructions#11

Open
see-dubya wants to merge 48 commits into
rosen-bridge:devfrom
see-dubya:dev
Open

Update Watcher deployment instructions#11
see-dubya wants to merge 48 commits into
rosen-bridge:devfrom
see-dubya:dev

Conversation

@see-dubya

@see-dubya see-dubya commented Mar 23, 2024

Copy link
Copy Markdown

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:

  1. Create local directory and files
  2. Create Watcher wallet and API Key hash
  3. Edit Watcher enviroment variable file
  4. Edit Watcher configuration file
  5. Pull and run Watcher application
  6. Get Permits

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

@TheStophe

TheStophe commented Dec 2, 2024

Copy link
Copy Markdown
Contributor

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, sudo cp -r watcher/ watcher-ada/

Then proceed to follow setup steps.

If you do the following:
~/rosenbridge/operation/watcher
~/rosenbridge-ada/operation/watcher

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.

@TheStophe

Copy link
Copy Markdown
Contributor

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.

bitcoin:
  type: rpc
  rpc:
    url: http://headless.local:8332  # Replace with the actual hostname or IP of the Bitcoin node
    username: bitcoinrpc  # Replace with your actual RPC username
    password: yourpassword  # Replace with your actual RPC password
  initial:
    height: <latest bitcoin height>

@TheStophe

Copy link
Copy Markdown
Contributor

Bumping this MR for an update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants