-
Notifications
You must be signed in to change notification settings - Fork 864
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
Enabling IPNS pubsub via daemon flags #1828
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
Thank you for the reply. I wasn't aware of the tray option. I found only CLI flag way of doing it. Since there are some issues with Electron tray and Linux distros it might not work on Linux. Is there any filtering of options/flag when the daemon is launched with IPFS Desktop. I tried the flags from the command line and it worked, it was just when the daemon was started via IPFS Desktop there was issues. |
I'm just a regular user and I'm not too familiar with CLI flags or IPFS on Linux, sorry! |
I'm closing this because the error was caused by manually changing config.json and introducing bug that way. Note that |
OS: Windows 10 Home 21H1 - build 19043.985
IPFS Desktop 0.15.0
Bug description
Cannot enable IPNS pubsub with
--enable-namesys-pubsub
daemon flag. Flag is added as noted in Which flags does IPFS Desktop boot with? .The GUI (cube) flashes 2-3 times and then continues as nothing happened. Desired feature is still disabled - using
ipfs name pubsub state
. Fileconfig.json
automatically resets to default configuration.To Reproduce
The flag
--enable-namesys-pubsub
is added to a fileC:\Users\<user>\AppData\Roaming\IPFS Desktop\config.json
.It doesn't matter in which position it is added. It only causes a more severe logdump if it is added directly after flag
--routing
.Expected behavior
I am not sure what the expected behavior is, probablly the feature being enabled. I am trying to get familiar with IPNS PubSub atm.
Logs
Faulty log
Additional context
I am exploring a distributed app idea. Users would periodically upload/make available some data via IPFS. Service would use IPNS to log/retrieve the latest submission. IPNS PubSub would be used to notify the service of new IPNS mapping. For now, users would use IPFS Desktop as their gateway, since it provides a nice GUI, makes IPFS more familiar to them. Later go-ipfs daemon could be included in a seperate executable. As noted in the documentation both the users and the service provider need to have the IPNS PubSub enabled in order for it to work as intended.
The text was updated successfully, but these errors were encountered: