-
Notifications
You must be signed in to change notification settings - Fork 428
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
[WIP] Adding a .env file for the Osmosis chain config #812
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I'm closing this PR in favor of one going to stage first. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following is an idea that would make DevOps automation a lot easier. Currently we have more than just a testnet, stage and prod environments for the frontend. We also have dedicated frontend environments for each chain release where we do full QA testing from the frontend.
Currently we have to manually create a branch and modify these values. We would like to propose moving the configuration to a .env file instead, where the defaults would point to mainnet.
The infra/devops team will be able to spin up v13, v14 via IAC:
Testing
Testnet config
Variables here:
3fa665a
Vercel Preview:
https://osmosis-frontend-3p6wrs1wz-osmo-labs.vercel.app/
Added successfully to Keplr and created a swap which directed to the correct mintscan page.
Mainnet config
Variables here:
96ce322
Vercel Preview:
https://osmosis-frontend-indqh5xot-osmo-labs.vercel.app/
Site added to the osmosis network config
![image](https://user-images.githubusercontent.com/13665117/191344853-228b20c0-35d3-480d-8107-b65125f64335.png)
There is additional IS_TESTNET login in the app that could be updated eventually but it's not necesary for spinning up new environments.
@niccoloraspa