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.

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

ipfs gateways should run ipfs-cluster. Ipfs pin-bot should take advantage. #155

Closed
hsanjuan opened this issue Sep 13, 2017 · 1 comment
Closed

ipfs gateways should run ipfs-cluster. Ipfs pin-bot should take advantage. #155

hsanjuan opened this issue Sep 13, 2017 · 1 comment
Assignees
@hsanjuan
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up
Milestone
IPFS gateways mig...

Comments

@hsanjuan
Copy link
Collaborator

This implies:

  • Making sure the gateways run cluster (probably the container, probably in standalone fashion - different container runs ipfs which needs to be upgradeable separately)
  • Upgrading ipfs pin-bot to use a single endpoint
  • Upgrading ipfs pin-bot to synchronously wait for things to be pinned and report otherwise (just like it does now).
    • This may mean figuring out a way for ipfs-cluster to provide a synchronous Pin() endpoint which only returns when things have correctly been pinned.
    • Or figuring out a way to subscribe to ipfs-cluster events which are then exported on a websocket (for example)
    • That sounds like a usecase for leveraging pub-sub.
@hsanjuan hsanjuan self-assigned this Sep 13, 2017
@hsanjuan hsanjuan added exp/wizard Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature labels Sep 13, 2017
@hsanjuan
Copy link
Collaborator Author

Gonna reserve this one for myself :)

@hsanjuan hsanjuan added this to the IPFS gateways migrated to ipfs-cluster [Q4O1] milestone Oct 10, 2017
@hsanjuan hsanjuan added status/ready Ready to be worked P1 High: Likely tackled by core team if no one steps up labels Oct 10, 2017
@hsanjuan hsanjuan added status/in-progress In progress and removed status/ready Ready to be worked labels Nov 20, 2017
@hsanjuan hsanjuan added need/review Needs a review and removed status/in-progress In progress labels Dec 1, 2017
@hsanjuan hsanjuan mentioned this issue Dec 1, 2017
Closed
@ghost ghost removed the need/review Needs a review label Dec 4, 2017
@ZenGround0 ZenGround0 mentioned this issue Dec 4, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hsanjuan hsanjuan

Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Milestone
IPFS gateways migrated to ipfs-cluster
Development

No branches or pull requests
1 participant
@hsanjuan