Skip to content
This repository was archived by the owner on Aug 12, 2020. It is now read-only.

Conversation

@whyrusleeping
Copy link
Contributor

This definitely needs some feedback, but i think that we need a guide like this to encourage people to build more awesome things on ipfs.

Copy link
Contributor

Choose a reason for hiding this comment

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

  • API_ORIGIN is deprecated. use the config var (see ipfs daemon).
  • we should not encourage *. it's a pretty big security hole. i can give you a single link that will delete all your pin set, gc, and then download a bunch of crap. So instead encourage to say:
ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin \
  '["http://localhost:<port>", "http://127.0.0.1:<port>", "http://127.0.0.1:$desired-port"]'

<port> is for the local api port. and $desired-port is for user's port.

@jbenet
Copy link
Contributor

jbenet commented Aug 5, 2015

Super good! 👍 i think we should cover also using the api. maybe the guide could actually guide the user through doing something very simple-- maybe building the peer globe or something. or a textarea "paste to ipfs" or something.

Copy link
Contributor

Choose a reason for hiding this comment

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

"provides an HTTP API for interacting with the daemon"

@RichardLitt
Copy link
Contributor

Can you give a fuller example with a mock webapp? Something like a tutorial, here?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants