hardhat-deploy VS dotenv

Attempting to implement this repository: https://github.com/wighawag/hardhat-deploy

or we can use the hardhat-deploy community plugin to deploy our contracts more professionally.

I imagine you have figured out how to do it by now. Consider using this plugin - https://github.com/wighawag/hardhat-deploy It will make your life easier and adds hre.getNamedAccounts() and hre.getUnnamedAccounts() Also it is exposed in the environment when running tests

Deploying consisted of using hardhat and its fantastic hardhat-deploy plugin to automagically manage deployments for us.

Next, lets install a package called hardhat-deploy which makes working with hardhat 2x easier & fun 👻

Hardhat-deploy now supports zkSync (Github)

Uses hardhat-deploy to keep track of deployments (upgradable or normal)

Once the hardhat project is initialized, Next we install hardhat-deploy which will make our life easier with deployments and tests😁

Install hardhat-deploy plugin as npm install hardhat-deploy and import it inside 'hardhat.config.js' file as:

Just found https://github.com/wighawag/hardhat-deploy, which is pretty much what I was looking for

This is the second part of my Test Driving a Rails API series. In Part 1 we set up our development environment, generated a Rails API-only application, installed dotenv to easily store configuration values in the environment, and installed and configured PostgreSQL version 16 as our database.

Storing environment variables for a Rails app can be problematic. The dotenv gem will automatically, when Rails boots, load environment variables from .env files into the Rails ENV. This is a great way to store private information that varies per developer or deployment environment, such as your development database configuration. Rails Encrypted Credentials is a great way to store private information, like API keys, etc, but I wouldn’t use it for storing my local development environment’s database information. The Encrypted Credentials file is checked into the git repository and would, therefore, be shared by all developers on the project. dotenv allows each developer or deployment environment to store their own information in .env files that are ignored by git.

dotenv

Install the dotenv gem.

dotenv-rails

Yeah, now that I think of it, it does require a gem. I have used this in most projects https://github.com/bkeepers/dotenv