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

Jump to bottom

add --allow-run and --allow-plugin env variables #32

Closed
littledivy opened this issue Aug 23, 2020 · 2 comments · Fixed by #33
Closed

add --allow-run and --allow-plugin env variables #32

littledivy opened this issue Aug 23, 2020 · 2 comments · Fixed by #33

Comments

@littledivy
Copy link

While trying to open a native plugin and spawning a sub process, vercel-deno does not provide the args for that. Maybe expose an env variable to do so?
@littledivy littledivy mentioned this issue Aug 23, 2020
Merged
TooTallNate added a commit that referenced this issue Aug 24, 2020
@TooTallNate
Use --allow-all
fd12c81 
Fixes #32.
@TooTallNate TooTallNate mentioned this issue Aug 24, 2020
Merged
@TooTallNate
Copy link
Collaborator

Might as well use --allow-all right? Since Lambda already provides a sandboxed environment. Let me know if #33 will work for you.

@littledivy
Copy link
Author

Yes, that would be great!

TooTallNate added a commit that referenced this issue Aug 24, 2020
@TooTallNate
Use --allow-all (#33)
488646f 
Fixes #32.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use --allow-all vercel-community/deno
2 participants
@TooTallNate @littledivy