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.

Sign up for GitHub

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

Clone the MerkleDAG node pointed by Castor IPNS #5

Closed
daviddias opened this issue Nov 20, 2015 · 2 comments
Closed

Clone the MerkleDAG node pointed by Castor IPNS #5

daviddias opened this issue Nov 20, 2015 · 2 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@daviddias
Copy link
Member

Castor will be constantly publishing the latest state of its npm registry mirror on its IPNS name.

registry-mirror --ipfs must copy that node. In ipfs CLI commands, it looks like this:

ipfs files cp /ipfs/`ipfs name resolve /ipns/QmdNc4B89DxVeiuDKRN5bWdKsAPCmekgmJMkRSdUNa7x9z` /npm-registry

QmdNc4B89DxVeiuDKRN5bWdKsAPCmekgmJMkRSdUNa7x9z is Castor's ID
@daviddias daviddias added the kind/enhancement A net-new feature or improvement to an existing feature label Nov 20, 2015
@daviddias
Copy link
Member Author

Important, when cloning do ipfs files mv /npm-registry /npm-registry.bak-<hash> and then the ipfs files cp to not loose what is already available.

Also, make sure to always connect to Castor first.

This was referenced Nov 23, 2015
Closed
Closed
@daviddias
Copy link
Member Author

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@daviddias