Skip to content

Port features from pl-diagnose #24

Closed
@laurentsenta

Description

@laurentsenta

We implemented pl-diagnose during launchpad as a "ipfs-check but easier to use",
We want to merge its features back into ipfs-check.

https://github.com/laurentsenta/pl-diagnose

API endpoints:

https://github.com/laurentsenta/pl-diagnose/blob/32be4cf13db63da02a5f626215f849c60f80a1b2/backend/main.go#L31-L49

  • /find?cid={cid}: Find a piece of content in the DHT
  • /find-peer?addr={peer-multiaddress}: Find a peer in the DHT
  • /identify?addr={peer-multiaddress}: Dial into the peer and use the identify protocol
  • /bitswap?addr={peer-multiaddress}&cid={cid}: Dial into the peer and try getting the content identified by the cid

Outputs & Implementations can be found in the daemon file.

UI / UX

Not sure what we want to do with the frontend. It made sense to use something familiar during launchpad,
a few things probably worth saving:

  • pl-diagnose is literally "ipfs-check but with smaller steps",
    • we try our best to test only 1 thing per step so that if something goes wrong, it's easier to tell why and how to fix it.
  • There is a link ❓ Need help with this result? Ask for help on github that generates an issue for the user.
  • Parameters are stored in the URI, easy to share,
  • We hoped to create a single location to share pl's diagnostics-related tools and made sure there's an easy way to contribute (https://pl-diagnose.on.fleek.co/#/toolbox)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions