-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tbc: allow seeds to be overwritten #158
Conversation
if cfg seeds are set, use those, otherwise use the defaults for the network chosen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will cfg.Seeds
be exposed via an environment variable?
If so, I think you need to add an item to the slice in cmd/tbcd/
ah yes I had forgottent we have the command (I was thinking of only |
Co-authored-by: Joshua Sing <joshua@bloq.com>
Co-authored-by: Joshua Sing <joshua@bloq.com>
Co-authored-by: Joshua Sing <joshua@bloq.com>
* allow TBC seeds to be overwritten if cfg seeds are set, use those, otherwise use the defaults for the network chosen * fixed missing seeding * remove tbc Server.port * using string for seeds * use host for lookupip * added TBC_SEEDS env config * Update service/tbc/tbc.go Co-authored-by: Joshua Sing <joshua@bloq.com> * simplify NewPeer in localPeerManager * Update cmd/tbcd/tbcd.go Co-authored-by: Joshua Sing <joshua@bloq.com> * use AppendSlice * removed ports from variables * fix reflect handling of seeds * Update config/config.go Co-authored-by: Joshua Sing <joshua@bloq.com> * using 127.0.0.1 as default IP/host for localnet --------- Co-authored-by: Joshua Sing <joshua@bloq.com>
Summary
allow tbc seeds to be overwritten
Changes
if cfg seeds are set, use those, otherwise use the defaults for the network chosen
fixes #157