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

Switch to Hardhat configuration variables instead of using .env #181

Open
andrejrakic opened this issue Feb 5, 2024 · 1 comment
Open

Comments

@andrejrakic
Copy link
Contributor

Update the project to support Hardhat configuration variables instead of using .env file(s)

@zeuslawyer
Copy link
Contributor

@andrejrakic
Wondering if there is any advantage to this since the vars are stored as plain tex, just the same as .env files?

Would using hardhat var offer any significant advantage to the developer, their learning or experience? or will it simply nudge developers towards switching from a workflow (.env files) they are already familiar with? We have observed that env-enc created the same "friction" given that devs were accustomed to .env files (even though env-enc had WAY more protection in the form of encryption).

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