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

fix(gw): remove hardcoded hostnames #8069

Merged
merged 1 commit into from
Apr 13, 2021
Merged

Conversation

lidel
Copy link
Member

@lidel lidel commented Apr 12, 2021

This PR closes #7317 by removing hard-coded PL hostnames from the default config, making the localhost the only implicit gateway hostname defined out-of-the-box.

@mburns to double-check if dweb.link uses explicit Gateway.PublicGateways config so it is not impacted by this change.

This closes #7317 by removing hardcoded PL hostnames from default
config, making the localhost the only implicit gateway hostname.
@lidel lidel marked this pull request as ready for review April 12, 2021 17:29
@mburns
Copy link
Contributor

mburns commented Apr 12, 2021

👍 to this change

Bifrost Infra explicitly managed the dweb.link and (gateway.)ipfs.io and their equivalent Staging counterparts.

@Stebalien Stebalien merged commit fb4542b into master Apr 13, 2021
@Stebalien Stebalien deleted the fix/remove-hardcoded-hostnames branch April 13, 2021 22:24
@aschmahmann aschmahmann mentioned this pull request May 14, 2021
71 tasks
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 this pull request may close these issues.

Even when explicitely set, the subdomain gateway config still include ipfs.io, gateway.ipfs.io and dweb.link
4 participants