Skip to content

Support custom dot-env files in edge functions #5638

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.

Sign up for GitHub

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
Closed
1 task done
danez opened this issue Apr 17, 2023 · 0 comments
Closed
1 task done

Support custom dot-env files in edge functions #5638

danez opened this issue Apr 17, 2023 · 0 comments
Assignees
@danez
Labels
area: edge-functions type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@danez
Copy link
Contributor

danez commented Apr 17, 2023

Which problem is this feature request solving?

Currently, only dot-env files starting with .env are supported.

Describe the solution you'd like

The detection of environment variables for edge functions depends on the source start with .env.

We should make another field that is not human-readable but only internal to detect where an environment variable comes from.

Pull request (optional)

  • I can submit a pull request.
@danez danez added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Apr 17, 2023
@danez danez self-assigned this Apr 17, 2023
@serhalp serhalp closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danez danez

Labels
area: edge-functions type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danez @serhalp