at least, when I iterate through the env object, it doesn't seem to have my secret
at least, when I iterate through the env object, it doesn't seem to have my secret
wrangler secret put SECRET_KEY and even though it seemed to push the secret, it doesn't seem like it workedapp.electron://, so I added app.electron), but still get the Invalid domain error when the app is packaged.
slotsNEXT_PUBLIC_ should work but is this a best practice for turnstiles? I can't find any documentation on nit
example.com and example.pages.dev and youre good to go with one sitekey/siteverify request multiple times, as long as the same idempotency_key is provided. I would probably place it as part of the form the user submits, so every submission includes the generated keyidempotency_key pre-set by the backendidempotency_key from form returns sucessidempotency_key returns sucessidempotency_key? Different form on the same page? Different form on a different page? Or a whole new user session?idempotency_key is there for when submission of the form/action can fail, even if the Turnstile check succeeds. For example, say you have a form with the following fields:idempotency_key to the form(in a hidden field), that persists on retry, then once the Turnstile Check is completed once, it can be reused(without failing) when a submission is retried<form> (that contains text box + content + submit button), each submit is technically a POST form submit, but SPA intercepted and processed (accordingly). Should each message submit contain a new turnstile challenge (as it is currently), or keep it the same challenge with the same idempotency_key (as a sort of per active session key or challenge expires - whichever comes first)?wrangler secret put SECRET_KEYapp.electron://app.electronInvalid domainslotsNEXT_PUBLIC_ example.comexample.pages.dev/siteverifyidempotency_keyidempotency_keyidempotency_keyidempotency_keyidempotency_keyidempotency_keyidempotency_keyidempotency_key<form>