Closed torkelrogstad closed 1 week ago
Currently we rely on the user having bdk-cli installed on their system. When we shell out we just use whatever is on the PATH: https://github.com/LayerTwo-Labs/sidesail/blob/1d67065b466a86c85540c2b7cfd594f7177039d6/drivechain-server/bdk/bdk.go#L65-L67
bdk-cli
Instead, we should be doing the following:
embed
Currently we rely on the user having
bdk-cli
installed on their system. When we shell out we just use whatever is on the PATH: https://github.com/LayerTwo-Labs/sidesail/blob/1d67065b466a86c85540c2b7cfd594f7177039d6/drivechain-server/bdk/bdk.go#L65-L67Instead, we should be doing the following:
bdk-cli
with the correct tags. It is fine for this script to assume that Rust is already installed.bdk-cli
if it does not exist.bdk-cli
into some sort of binary assets folder that's ignored by Gitembed
in the Go standard librarybdk-cli
, do this through this embedded binary