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 Jul 27, 2021. It is now read-only.
I ran the envsubst, and the yaml had empty fields. and as you would expect, the subsequent ecs-cli command failed.
So maybe some sort of check that the vars exist, saving them to the .bash_profile or just forcing the user to re-set the vars again would be good here.
The text was updated successfully, but these errors were encountered:
At https://ecsworkshop.com/nodejs/backend/#deploy-frontend-1 I ran into an issue while creating the service using the ecs-cli fargate mode path.
I had closed the terminal I used to setup Frontend, so I lost the vars I had set previously on the:
https://ecsworkshop.com/frontend/frontend/#deploy-frontend-1 > Set environment variables from our build section.
I ran the envsubst, and the yaml had empty fields. and as you would expect, the subsequent ecs-cli command failed.
So maybe some sort of check that the vars exist, saving them to the .bash_profile or just forcing the user to re-set the vars again would be good here.
The text was updated successfully, but these errors were encountered: