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

[DOCUMENTATION] Custom chain from .env #251

Open
ZAlexanderV opened this issue Oct 9, 2024 · 3 comments
Open

[DOCUMENTATION] Custom chain from .env #251

ZAlexanderV opened this issue Oct 9, 2024 · 3 comments

Comments

@ZAlexanderV
Copy link

Is it possible to add custom chains from .env file and disable cosmos registry?
Can anyone provide an example .env file for a custom network?

@abefernan
Copy link
Contributor

Yes. You can set NEXT_PUBLIC_MULTICHAIN=false and that will disable the chain selection menu. Data will be queried from the chain-registry, still. In order to use a custom network you can also set some more variables on the envfile, you can see them in this function prefixed with NEXT_PUBLIC_ (this is not documented anywhere, sorry about that!).

@ZAlexanderV
Copy link
Author

ZAlexanderV commented Oct 11, 2024

I constructed .env.local with values from function, but seems code is broken.
Prefix, Chain name are not applied and not working.
Same values entered in the modal form works fine.

@abefernan
Copy link
Contributor

Have you tried navigating directly to <url>/<my-registry>, where url would be your localhost or wherever you are hosting it, and my-registry would be the value of NEXT_PUBLIC_REGISTRY_NAME in your envfile (and not named like another chain from the registry)? I tried that and it loaded the values correctly

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

No branches or pull requests

2 participants