-
Notifications
You must be signed in to change notification settings - Fork 16
use embedded dmsghttp config for dmsg utilities [WIP] #298
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
Conversation
|
@mrpalide I have significantly refactored the code for dmsgcurl. Can you check on this error? I can't seem to figure it out This will produce the error Error not present with the -z flag which is the original / previous behavior of dmsgcurl, using the dmsg-discovery as normal |
|
Seems solved. |
|
@mrpalide can you test this when you get a chance. The server side doesn't seem to work via dmsg-direct and I can't figure out why. Then in a different terminal try to fetch the README.md from the server public key That fails, for me, but if I switch the server to use the discovery it does work |
this attempts to add to dmsg functionality that currently exists for skywire. Using the embedded dmsg servers of the dmsghttp-config.json it should be possible to connect to dmsg without http request to the dmsg discovery.
Testing
the default behavior is to avoid http requests. The
-zflag switches to using http request & the discovery.It's not yet working