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
We build a Docker image and push it to AWS for use in the production app, but this sits inside a private ECR repository.
It could be useful to have the image on a public repo as well. Based on the work from cal-itp/eligibility-server#22, we can add an additional docker/build-push-action step to our dev deployment that pushes into the GitHub Container Registry:
We build a Docker image and push it to AWS for use in the production app, but this sits inside a private ECR repository.
It could be useful to have the image on a public repo as well. Based on the work from cal-itp/eligibility-server#22, we can add an additional
docker/build-push-action
step to ourdev
deployment that pushes into the GitHub Container Registry:We can do this for each of our 3 environments to always have the current image running in each environment, available in GHCR as well.
Since #135 landed, additional
docker/build-push-action
steps should go very fast.The text was updated successfully, but these errors were encountered: