Here's an attempt to consolidate existing scripts to a single file, which would be a little easier to include in a release tarball (see #76). Reviewing the script will make the most sense if you start with the dopplerctl() function near the bottom (line 198ish). If you prefer the existing setup, no worries we can bundle those individual scripts instead, and feel free to let me know any related script improvements you'd find helpful.
Reproduces the functionality of existing scripts with slightly different syntax:
aliases.sh
converter.sh
docker_clear.sh
ping_test.sh
reset.sh
volumes_clear.sh
Source the file, then use dopplerctl to run the functions as subcommands:
source dopplerctl.sh && dopplerctl
1-level completion is available for bash (not passed through to subcommands yet):
source <(dopplerctl completion bash)
I've been waiting to resolve one last TODO before opening this:
reconcile scripts expecting signet, and binary+doppler_files using regtest
...I think it'd help to get your input on expected usage, and we can set the default network based on that.
References:
shift builtin used for calling a function based on subcommand parameter
Hey just taking a look at this, the default network can be assumed to be regtest (normally people will probably use doppler just on their local cluster of nodes not connected to a wider network)
Here's an attempt to consolidate existing scripts to a single file, which would be a little easier to include in a release tarball (see #76). Reviewing the script will make the most sense if you start with the
dopplerctl()
function near the bottom (line 198ish). If you prefer the existing setup, no worries we can bundle those individual scripts instead, and feel free to let me know any related script improvements you'd find helpful.Reproduces the functionality of existing scripts with slightly different syntax:
Source the file, then use
dopplerctl
to run the functions as subcommands:1-level completion is available for bash (not passed through to subcommands yet):
I've been waiting to resolve one last TODO before opening this:
...I think it'd help to get your input on expected usage, and we can set the default network based on that.
References:
shift
builtin used for calling a function based on subcommand parameter