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.

Sign up for GitHub

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

Jump to bottom

qri repo initialization should come with at least one default dataset #161

Closed
b5 opened this issue Dec 8, 2017 · 0 comments · Fixed by #164
Closed

qri repo initialization should come with at least one default dataset #161

b5 opened this issue Dec 8, 2017 · 0 comments · Fixed by #164
Assignees
@b5
Milestone
0.1.0

Comments

@b5
Copy link
Member

b5 commented Dec 8, 2017

when an empty qri repo is detected (as in, no config file is present), we should fetch & add a dataset from the network.
@b5 b5 added this to the 0.1.0 milestone Dec 8, 2017
@b5 b5 self-assigned this Dec 8, 2017
@b5 b5 added the in progress label Dec 8, 2017
b5 added a commit that referenced this issue Dec 8, 2017
@b5
feat(DefaultDatasets): first cuts on requesting default datasets
05a9e2f 
when no config file is present on any CLI command, attempt to
spin up a repo & grap default hashes. This'll definitly break
stuff but we got a demo today so whatever

closes #161
@b5 b5 mentioned this issue Dec 8, 2017
Merged
@b5 b5 closed this as completed in #164 Dec 12, 2017
@ghost ghost removed the in progress label Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@b5 b5

Labels
None yet
Projects
None yet
Milestone
0.1.0
Development

Successfully merging a pull request may close this issue.

feat(RPC): change default port, provide RPC listener qri-io/qri
1 participant
@b5