Skip to content

feat: add back controller.api.gatewayHost and controller.api.gatewayPort or similar #831

@SgtPooki

Description

@SgtPooki

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:

const gwMatch = output.trim().match(/Gateway .*listening on:? (.*)/)

Metadata

Metadata

Assignees

Labels

P1High: Likely tackled by core team if no one steps upeffort/hoursEstimated to take one or several hoursexp/intermediatePrior experience is likely helpfulhelp wantedSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featurestatus/in-progressIn progresstopic/devexpDeveloper Experience

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions