Skip to content
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

re-externalize qri config file and add qri bootstrap #108

Closed
b5 opened this issue Nov 9, 2017 · 0 comments · Fixed by #110
Closed

re-externalize qri config file and add qri bootstrap #108

b5 opened this issue Nov 9, 2017 · 0 comments · Fixed by #110
Assignees
Milestone

Comments

@b5
Copy link
Member

b5 commented Nov 9, 2017

ok so our qri gateway node had a memory leak & died, which means that hard-coded bootstrap address is toast, which means qri is totally broken. We need qri bootstrap to deal with this in a more complete way

@b5 b5 added this to the 0.1.0 milestone Nov 9, 2017
@b5 b5 self-assigned this Nov 9, 2017
b5 added a commit that referenced this issue Nov 9, 2017
thanks to gateway nodes dying, we need a way to modify our bootstrap list.
To do this the right way, I've brought back config.json, this time stored
in $QRI_PATH.
We've also added a new command "boostrap" that allows listing, adding,
and removing bootstrap addresses.

closes #108
b5 added a commit that referenced this issue Nov 9, 2017
thanks to gateway nodes dying, we need a way to modify our bootstrap list.
To do this the right way, I've brought back config.json, this time stored
in $QRI_PATH.
We've also added a new command "boostrap" that allows listing, adding,
and removing bootstrap addresses.

closes #108
@b5 b5 closed this as completed in #110 Nov 9, 2017
@ghost ghost removed the in progress label Nov 9, 2017
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 a pull request may close this issue.

1 participant