Skip to content
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.

Improving js-ipfs init #22

Closed
daviddias opened this issue Mar 10, 2017 · 2 comments
Closed

Improving js-ipfs init #22

daviddias opened this issue Mar 10, 2017 · 2 comments
Assignees
@daviddias
Milestone
The Docs are less...

Comments

@daviddias
Copy link

We want to improve the js-ipfs init sequence and we have a clear vision of how that should happen that has been discussed here: ipfs/js-ipfs#556

This requires writing code, but it will greatly simplify the documentation of using a js-ipfs node. I believe it will be valuable for this Sprint. I can tackle it :)
@daviddias daviddias self-assigned this Mar 10, 2017
@flyingzumwalt flyingzumwalt modified the milestone: The Docs are Not a Disaster Mar 10, 2017
@ghost ghost added the ready label Mar 10, 2017
@daviddias daviddias mentioned this issue Mar 14, 2017
Merged
@daviddias
Copy link
Author

Work happening here: ipfs/js-ipfs#790

@daviddias
Copy link
Author

Done \o/

@daviddias daviddias removed the ready label Mar 15, 2017
@snyk-bot snyk-bot mentioned this issue May 22, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@daviddias daviddias

Labels
None yet
Projects
None yet
Milestone
The Docs are less confusing
Development

No branches or pull requests
2 participants
@flyingzumwalt @daviddias