Skip to content

Self-hosted VS Deno Deploy #103

@perguth

Description

@perguth

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.

image

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions