You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's common to have secrets available as a file or similar when deploying a service (as explained in #174 (comment)). I'd like to be able to source the Turnstile secret key from such a file in production.
馃啎 The solution you'd like
In #174 we added secret sourcing to the module code, which runs at build time. I now noticed that secret sourcing doesn't work at runtime, at which it makes most sense. It would be beneficial if the secret key could be sourced in the Nitro verify util (instead).
馃攳 Alternatives you've considered
Warn for no secret key when building for production: #296
Also, should we continue to just use node:fs when a secret key path is given or could we make use of something like unstorage maybe? Don't know if I understand that tool correctly.
The text was updated successfully, but these errors were encountered:
馃啋 Your use case
It's common to have secrets available as a file or similar when deploying a service (as explained in #174 (comment)). I'd like to be able to source the Turnstile secret key from such a file in production.
馃啎 The solution you'd like
In #174 we added secret sourcing to the module code, which runs at build time. I now noticed that secret sourcing doesn't work at runtime, at which it makes most sense. It would be beneficial if the secret key could be sourced in the Nitro
verify
util (instead).馃攳 Alternatives you've considered
Warn for no secret key when building for production: #296
鈩癸笍 Additional info
cc @danielroe
Also, should we continue to just use
node:fs
when a secret key path is given or could we make use of something likeunstorage
maybe? Don't know if I understand that tool correctly.The text was updated successfully, but these errors were encountered: