Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self-hosted VS Deno Deploy #103

Open
perguth opened this issue Nov 23, 2024 · 0 comments
Open

Self-hosted VS Deno Deploy #103

perguth opened this issue Nov 23, 2024 · 0 comments

Comments

@perguth
Copy link

perguth commented Nov 23, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant