Skip to content
This repository has been archived by the owner on Nov 5, 2022. It is now read-only.

Steps to build this tool #1

Closed
akshaysuryawanshi opened this issue Jan 29, 2019 · 6 comments
Closed

Steps to build this tool #1

akshaysuryawanshi opened this issue Jan 29, 2019 · 6 comments

Comments

@akshaysuryawanshi
Copy link

This is pretty exciting tool, I wanted to start testing it, any estimates on when the steps to build it will be available as part of the README.

@pivanof
Copy link
Contributor

pivanof commented Jan 30, 2019

Good point. :)
I'll look into adding instructions into README. In short: you need to install Bazel (see https://docs.bazel.build/versions/master/install.html) and run "bazel build ..." in the directory with mysql-ripple sources. You can find some pretty good quickstart guide of how to work with Bazel at https://abseil.io/docs/cpp/quickstart, there's also Bazel tutorial at https://docs.bazel.build/versions/master/tutorial/cpp.html.

@codedumper1
Copy link
Contributor

This is pretty exciting tool, I wanted to start testing it, any estimates on when the steps to build it will be available as part of the README.

I made PR, instructions are here -
1ffe1a1

@akshaysuryawanshi
Copy link
Author

Thanks 👍 I can confirm the instructions work as expected. And started exploring the tool, it seems like rippled doesnt use a password field for connection. Any idea if there is a plan to add support for that in it?

@pivanof
Copy link
Contributor

pivanof commented Jan 31, 2019

There is a tentative plan to support passwords, but I can't say when we can get to it. Inside Google we use ALTS for authentication (see https://security.googleblog.com/2017/12/securing-communications-between-google.html), so adding password support wasn't that high on the priority list. Contributions are welcome.

@dveeden
Copy link
Contributor

dveeden commented Feb 3, 2019

I extended the README in my branch: dveeden@9f6aa4f

@pivanof
Copy link
Contributor

pivanof commented Mar 2, 2019

@dveeden I've merged #2 by @codedumper1, so I will close this issue. But please feel free to propose any additional adjustments to the README file if you think it's necessary.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants