replying to @dtinth
Yes, good idea. Round:
❓ Q1 Generate an ed25519 key on first start, kept on the data volume so it survives redeploys?
➡️ yes
❓ Q2 Remove BRIDGE_SSH_PRIVATE_KEY entirely (no env key path)?
➡️ yes…
bbc1179
echo something | ssh remote commit. Not sure if agent forwarding…
ssh-keygen -Y sign signature, and the script already signs through an agent, so the server could reuse your forwarded agent:
↳…ssh -A posted commits to a local dev-null.
One change to Q5: ssh logs in with the first key in your agent, which may not be your GitHub key. So the server asks dev-null's key-lookups which agent key is…commit bbc1179
