-
Notifications
You must be signed in to change notification settings - Fork 63
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulhelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/in-progressIn progressIn progresstopic/devexpDeveloper ExperienceDeveloper Experience
Description
With the latest update from #823 we no longer have the ability to get the listening ipfs gateway host and port from the instantiated kubo node.
this forces consumers to do handle passing around port/host config passed to createNode
or parsing config options from the created KuboNode
using https://github.com/multiformats/js-multiaddr-to-uri
We shouldn't need to do this on the consumer side because ipfsd-ctl and kubo-rpc-client should both have the gateway URL readily accessible.
We should expose this on the await node.info()
result.
Note: this used to be done by reading stdout:
js-ipfsd-ctl/src/ipfsd-daemon.ts
Line 250 in 6e0d0b5
const gwMatch = output.trim().match(/Gateway .*listening on:? (.*)/) |
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hoursexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulhelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/in-progressIn progressIn progresstopic/devexpDeveloper ExperienceDeveloper Experience