docs: keep the bridge secret on the service definition, not the host file - #90
Conversation
…file The host file is rewritten from Zo's managed secrets, so a value appended by hand disappears and the bridge dies at its next restart. Record where the secret belongs and how to rotate it against Vercel.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request updates the documentation for
Reviewers should begin by examining the changes in |
|
This pull request updates the documentation for
Reviewers should begin by examining the changes in |
The host secrets file is rewritten from Zo's managed secrets, so a hand-appended
DISCORD_BRIDGE_SECRETdisappears within hours. The running bridge keeps signing with the copy it read at startup, then fails at its next restart — which any push to this repository triggers via the deploy workflow.This documents where the secret belongs (the service definition), how to rotate it against Vercel, and the cheapest way to prove both sides agree without dispatching a turn.