We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried using this link, https://github.com/libp2p/go-libp2p-daemon/blob/master/specs/CONFIG.md, to test how to running configuration, but I got error message. $ p2pd -f ./DO.json 2021/02/16 11:52:18 failed to parse multiaddr "\"/unix/tmp/p2pd.sock\"": must begin with /
$ p2pd -f ./DO.json 2021/02/16 11:52:18 failed to parse multiaddr "\"/unix/tmp/p2pd.sock\"": must begin with /
How would I get this issue resolved? And is it possible to have something like the below in configuration file?
{ "ID": "Qma3GsJmB47xYuyahPZPSadh1avvxfyYQwk8R3UnFrQ6aP" "PublicKey": 'xxxxxxxxx', "PrivateKey" : "yyyyyyyyyy", }
Thanks
The text was updated successfully, but these errors were encountered:
to test how to running configuration, but I got error message
You have quoted your multiaddr twice, remove the extra quotes.
And is it possible to have something like the below in configuration file?
No. You need set the config's ID property to a path to a libp2p key file. You can generate a key with the p2p-keygen tool (in this repo).
ID
p2p-keygen
I've filed an issue to document this better: #247.
Sorry, something went wrong.
@Stebalien Thanks so much!
Stebalien
No branches or pull requests
I tried using this link, https://github.com/libp2p/go-libp2p-daemon/blob/master/specs/CONFIG.md, to test how to running configuration, but I got error message.
$ p2pd -f ./DO.json 2021/02/16 11:52:18 failed to parse multiaddr "\"/unix/tmp/p2pd.sock\"": must begin with /
How would I get this issue resolved? And is it possible to have something like the below in configuration file?
Thanks
The text was updated successfully, but these errors were encountered: