-
Notifications
You must be signed in to change notification settings - Fork 33
Open
Description
When connecting to a self-hosted instance DENO_KV_ACCESS_TOKEN
needs to be set for secure setup but on Deno Deploy that's an invalid key since DENO_
is a reserved prefix.
Setting the environment variable at runtime is also prohibited because of the prefix.
And the NPM build that allows passing in the token on instantiation seems not to work on Deno Deploy ("This API is not supported in this environment").
What to do?
laltin, argshook and megantshine-on-me
Metadata
Metadata
Assignees
Labels
No labels