[OP Stack Deployment] Issue with OP Stack Smart Contract Deployment on a localNet with "DEPLOY_CONFIG_PATH" #518
Replies: 2 comments 3 replies
-
https://docs.optimism.io/builders/chain-operators/features/custom-gas-token#deploying-your-contracts
|
Beta Was this translation helpful? Give feedback.
-
Giving an update on this discussion, depending on the environment sometimes some variables are not set properly even when they are exported. as a workaround and since this is a local dev network, putting a static value to a function can help move and deploy what is necessary. function deployConfigPath() internal pure returns (string memory _env) {
_env = "deploy-config/devnetL1.json";
} |
Beta Was this translation helpful? Give feedback.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
have an issue with OP Stack Smart Contract Deployment on a localNet. the
"DEPLOY_CONFIG_PATH=<PATH_TO_MY_DEPLOY_CONFIG>"
driving me a bit crazy.Used different values, and adjusted the filesystem rights as needed but still blocking.
Checked the
Config.sol
to see if there's any hints at thedeployConfigPath
function, nothing helping.If someone have any hints 🙏🏻
Logs
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions