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
Currently, ts-template uses a separate deploy repo to deploy to AWS. This repo contains GitHub workflows which build and deploy to AWS. The problem is that we are unable to modify the build configuration for the build and deploy steps because they are defined in this repo to be used with all ts-template projects.
The relevant code can be found in this workflow file:
This is a problem in particular for frontend projects which want to use non-secret frontend environment variables (such as for Supabase, Datadog RUM, etc.) because we are unable to specify build arguments to the Docker build step.
Expected behavior
There should be an easy way for projects using ts-template to expose frontend env vars in the frontend build step
The text was updated successfully, but these errors were encountered:
Problem
Currently, ts-template uses a separate
deploy
repo to deploy to AWS. This repo contains GitHub workflows which build and deploy to AWS. The problem is that we are unable to modify the build configuration for the build and deploy steps because they are defined in this repo to be used with all ts-template projects.The relevant code can be found in this workflow file:
This is a problem in particular for frontend projects which want to use non-secret frontend environment variables (such as for Supabase, Datadog RUM, etc.) because we are unable to specify build arguments to the Docker build step.
Expected behavior
There should be an easy way for projects using ts-template to expose frontend env vars in the frontend build step
The text was updated successfully, but these errors were encountered: