WIP: Set native IPFS peering config #9

Draft
raucao wants to merge 3 commits from feature/ipfs_peering into master
Owner

This is not intended to be merged, but just to back up and share what I think is the correct (unfinished) code for this.

Unfortunately, go-ipfs panics when setting the Peering.Peers config, even though you can .get() the peers this way, so it doesn't currently work with the release that introduced the feature.

closes #8

This is not intended to be merged, but just to back up and share what I think is the correct (unfinished) code for this. Unfortunately, go-ipfs panics when setting the `Peering.Peers` config, even though you can `.get()` the peers this way, so it doesn't currently work with the release that introduced the feature. closes #8
Author
Owner

I documented how to manually configure peering on the wiki now:

https://wiki.kosmos.org/Kredits:IPFS#Peering_with_Kosmos_IPFS_nodes

I think the program should probably just tell the user to configure this themselves for now.

I documented how to manually configure peering on the wiki now: https://wiki.kosmos.org/Kredits:IPFS#Peering_with_Kosmos_IPFS_nodes I think the program should probably just tell the user to configure this themselves for now.
This pull request has changes conflicting with the target branch.
  • index.js
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b feature/ipfs_peering master
git pull origin feature/ipfs_peering

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff feature/ipfs_peering
git push origin master
Sign in to join this conversation.
No description provided.