Fixing source mismatch with the container.#1107
Conversation
|
@EmrePiconbello is attempting to deploy a commit to the Mina Foundation's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
I just go over again and looks like we are creating the private key in /data/.mina-config while whole container and logs outputs etc happens on /root/.mina-config which is on normal docker documentation with --mount "type=bind,source=$(pwd)/.mina-config,dst=/root/.mina-config" \ I am not sure which part of this docker compose should change but it should be in parity with the rest. |
|
@EmrePiconbello yes, I also have this feeling that we should use /root/.mina-config/ can you also fix remaining places where /data/.mina-config/ is used? |
…config The container's home directory is /root, so .mina-config lives at /root/.mina-config. Updates volume mounts and internal path references across all affected docs pages. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
@dkijania This doesn't look exactly right for me but it's been so long since I made the deployment. I remember the reasons behind this PR but leaving rest of the edits to you as. Looks fine but feels of to me. |
2 participants
No description provided.