-
Notifications
You must be signed in to change notification settings - Fork 14
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
docker setup #48
base: develop
Are you sure you want to change the base?
docker setup #48
Conversation
…s into CCP-Red-Dragon/DockerV2
…s into CCP-Red-Dragon/DockerV2
|
||
ENV PATH="/root/.foundry/bin:${PATH}" | ||
|
||
ENTRYPOINT ["tail", "-f", "/dev/null"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove this since this is being built elsewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this docker file anymore ?
@@ -12,13 +12,17 @@ PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 | |||
WORLD_ADDRESS=0x8a791620dd6260079bf849dc5567adc3f2fdc318 | |||
PLAYER_PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 | |||
|
|||
#Docker RPC | |||
RPC_URL="http://foundry:8545" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will break the deploy:local script for those that are not on the docker network, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to remove this from the env and pass in with a special deploy:builder_env command. I know its not the nicest approach.
No description provided.