Replies: 1 comment
-
I found this related issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a set of "modules", and each module consists of a set of contracts, with inter-dependencies.
We started with
hardhat
years ago. Each module is anpm
package.Each package is published to
npmjs.com
, and contains: solidity code, ABIs, bindings and deployment files produced byhardhat-deploy
(json files).A year ago we partially switched to forge, mainly for testing.
We didn't abandon hardhat completely because of deployment.
Since then I see forge evolved and now we have
forge script
, which is the recommended way of handling more complex deployments, instead of just callingforge create
.My question is how do we organize complex deployment scenarios.
Do all deployments need to be executed in a single script class, or can we chain scripts somehow?
Can we store and load
broadcast
files somehow, so one script use deployment information from a previous one?Can we use
fork
somehow in this scenario? Is there any mechanism to know the address of a previously deployed contracts?Beta Was this translation helpful? Give feedback.
All reactions