-
Notifications
You must be signed in to change notification settings - Fork 757
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
🚀 Feature Request: Load dev https certificate and key from environment variables #5997
Comments
We discussed this in #4475 (comment). |
Command line arguments works fine but environment variables would be far more convenient. Also with the latter you don't need to add args to the |
…nment variables As well as providing paths to custom HTTPS certificate files, it is now possible to use WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH environment variables. Specifying the file paths at the command line overrides specifying in environment variables. Fixes #5997
…iables (#6479) * test: add http-options tests for providing explicit paths to files * feat: allow HTTPS custom certificate paths to be provided by a environment variables As well as providing paths to custom HTTPS certificate files, it is now possible to use WRANGLER_HTTPS_KEY_PATH and WRANGLER_HTTPS_CERT_PATH environment variables. Specifying the file paths at the command line overrides specifying in environment variables. Fixes #5997 * test: use `vi.stubEnv()` rather than manually hacking `process.env` in Wrangler tests This helper from Vitest will automatically revert to the original process.env values after each test.
Hey @petebacondarwin was this feature mentioned in the docs? |
I'm afraid not. In general we have not documented these types of env variable. @lrapoport-cf - is this something we should do? |
Describe the solution
I use Tailscale for https during development and have a common certificate and key for all projects. It would be convenient to load these using environment variables like
WRANGLER_HTTPS_{CERT|_KEY}_PATH
.The text was updated successfully, but these errors were encountered: