Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Tutorial: transfer-files #791

Merged
merged 1 commit into from
Mar 21, 2017
Merged

Tutorial: transfer-files #791

merged 1 commit into from
Mar 21, 2017

Conversation

daviddias
Copy link
Member

@daviddias daviddias commented Mar 15, 2017

TODO

  • Take out the yarn.lock
  • Peers list have a comma between every peer that is not supposed to be there
  • Multiaddr input is too wide and goes outside the containing box
  • Refactor code + add valuable comments
  • Have .get actually work with just one file
  • Fix drag-and-drop not closing popup when ending up not dropping file in UI
  • Finish tutorial in readme.md

@daviddias
Copy link
Member Author

@dignifiedquire minding reviewing the code for the example and putting some of your front end dev fairy dust? Looking to optimize for:

  • clarify
  • organization
  • code over comments

@daviddias
Copy link
Member Author

All right, this is now on 'mergeable' state. I feel it is not perfect and I believe we can do so much better when it comes to show how to work with ipfs, from explanations, code clarity and purpose of the demo, nevertheless, this is a great step forward as it was proven during the eth+ipfs hackweek, where this example was base for the networking demo described in https://blog.ethereum.org/2017/03/21/ethereum-js-ecosystem-updates/.

Thank you @dignifiedquire @victorbjelkholm @haadcode and @RichardLitt for putting work onto this endeavour ❤️


This will set up your IPFS repo in your home directory.

### 2. Make your daemons listen on WebSockets
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only applicable for Go right since JS sets this up automatically if I remember correctly?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point!


### 4. Dial to a node using WebSockets (your Desktop ones)

On your local node, run `ipfs id` to find the WebSockets address that it is listening on. Should look like this: `"/ip4/127.0.0.1/tcp/4003/ws/ipfs/<your peer id>".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change local node to desktop node or terminal node might be better, since local node could also refer to the one in the browser.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed :)

@daviddias daviddias merged commit 92d3fbe into master Mar 21, 2017
@daviddias daviddias deleted the docs/example/transfer-files branch March 21, 2017 17:25
@daviddias daviddias removed status/in-progress In progress labels Mar 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants