Skip to content
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

Support for custom API path #1389

Closed
calikevuche opened this issue Jan 28, 2020 · 1 comment · Fixed by #1613
Closed

Support for custom API path #1389

calikevuche opened this issue Jan 28, 2020 · 1 comment · Fixed by #1613
Milestone

Comments

@calikevuche
Copy link

Hi,

I have changed the location of the go-ipfs daemon. For example, this is what I get in the networks tab in browser when launching webui.

POST http://localhost:3000/api/v0/stats/bw?stream-channels=true net::ERR_CONNECTION_REFUSED

I would like to have the webui access a similar location, but with /v1/ instead of /v0/. Is there a away to change this to /v1/ in the ipfs-webui code, or otherwise, so that the webui can access the endpoint ?

@lidel
Copy link
Member

lidel commented Sep 10, 2020

FYSA when #1613 ships with v2.11, it will be possible to pass custom apiPath by defining API on Settings screen:

@lidel lidel changed the title Changing API references from v0 to v1 Support for custom API path Sep 10, 2020
@lidel lidel added this to the v2.11 milestone Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants