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

[WIP] Adding a .env file for the Osmosis chain config #812

Closed
wants to merge 13 commits into from

Conversation

daniel-farina
Copy link
Contributor

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:

  • Fully functional chain with a fresh copy from mainnet
  • front-end
  • and faucet if needed

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.

image

Mainnet config

Variables here:
96ce322
Vercel Preview:
https://osmosis-frontend-indqh5xot-osmo-labs.vercel.app/

Site added to the osmosis network config
image

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

@vercel
Copy link

vercel bot commented Sep 20, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
osmosis-frontend ✅ Ready (Inspect) Visit Preview Sep 22, 2022 at 7:47AM (UTC)
osmosis-frontier ✅ Ready (Inspect) Visit Preview Sep 22, 2022 at 7:47AM (UTC)

@daniel-farina
Copy link
Contributor Author

I'm closing this PR in favor of one going to stage first.
#824

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.

1 participant