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
{{ message }}
This repository has been archived by the owner on Oct 26, 2023. It is now read-only.
The web has odd approaches for using a different set of environment variables for production builds. This is particularly important if you are using third part services like Stripe.
The task at hand is to explore what is the optimal way to provide environment variables for various environment, considering:
CI/CD pipeline for building the front end apps
Potentially being run on Github actions
Avoid adding additional tooling to achieve management of environment vars
The text was updated successfully, but these errors were encountered:
initially it was the non-ssl endpoint causing the preflight call to fail and
subsequently turns out that the axios global configuration adding the authorization
header to the s3 file upload causing to be treated as a bad request.
we should develop a standad s3 bucket policy as part of REFS #19 for use against
projects
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The web has odd approaches for using a different set of environment variables for production builds. This is particularly important if you are using third part services like Stripe.
The task at hand is to explore what is the optimal way to provide environment variables for various environment, considering:
The text was updated successfully, but these errors were encountered: