feat: read the bridge's bot token and bridge secret from the host secrets file - #88
Conversation
…rets file A Zo process service starts from a bare environment: it inherits neither the host shell nor the deployment's Vercel variables, and the token and shared secret are stored there as sensitive values that cannot be read back. Load them from /root/.zo_secrets instead, so the service definition carries only the non-secret routing configuration. The environment still wins over the file.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request modifies the Discord Gateway bridge to read
Reviewers should begin by examining |
1 similar comment
|
This pull request modifies the Discord Gateway bridge to read
Reviewers should begin by examining |
The Discord Gateway bridge runs as a Zo
processservice, which starts from a bare environment: it inherits neither the host shell nor the deployment's Vercel variables.DISCORD_BOT_TOKENandDISCORD_BRIDGE_SECRETexist on Vercel as sensitive values that cannot be read back, so a service definition could not carry them.lib/host-secrets.tsreads them from/root/.zo_secrets— the same file the other Zo-hosted bots load — before anything reads the environment. An environment value always wins over the file, andZO_SECRETS_PATHoverrides the location, so both the service definition and the file stay able to supply any value.This makes the bridge registrable without duplicating credentials into the service definition.