DA-608 Update tezosconnect volumes #321
Conversation
Signed-off-by: Dzianis Andreyenka <[email protected]>
Signed-off-by: Dzianis Andreyenka <[email protected]>
denisandreenko
force-pushed
the
patch/tezos-config
branch
from
902c018
to
9268f67
Compare
|
@denisandreenko a description would be useful here and renaming the PR to what the change is doing. From what I can see you are splitting out the volumes for the DB from the config that gets mounted from the runtime directory |
| }, | ||
| Logging: docker.StandardLogOptions, | ||
| Environment: s.EnvironmentVars, | ||
| }, | ||
| VolumeNames: []string{ | ||
| fmt.Sprintf("tezosconnect_config_%s", member.ID), |
There was a problem hiding this comment.
What happened to this volume? Does it still get created? I do not see code to remove the creation of that volume
There was a problem hiding this comment.
If you see the code above - we use binding instead of mount for the connector configuration.
It allows us to update the config from the host machine.
We're using the same approach for the evmconnect now as well
|
Hey @EnriqueL8 |
No description provided.