Thank you for making Forge — it’s my first time using it, and so far it has been great.
I particularly love the smart image tagging that Forge does based on clean/dirty git status, so I use forge build locally very often. However, my project uses AWS ECR and my images are quite large (two images at ~1GB each), so the push step takes a long time on my connection. During development, I don’t always want to do this when I build an image—often I am just iterating locally and trying things out.
Could you perhaps add a --skip-push option to forge build, which would skip the step of pushing to the configured repository? That way, I could run forge build --skip-push while I am working on the project and iterating locally, and once I am ready to make my images available for deployment, I would run a regular build to push the image to ECR.
After a disappointing lack of any response whatsoever from the maintainers for over a year, I no longer consider this relevant and no longer use forge.
Thank you for making Forge — it’s my first time using it, and so far it has been great.
I particularly love the smart image tagging that Forge does based on clean/dirty git status, so I use
forge build
locally very often. However, my project uses AWS ECR and my images are quite large (two images at ~1GB each), so the push step takes a long time on my connection. During development, I don’t always want to do this when I build an image—often I am just iterating locally and trying things out.Could you perhaps add a
--skip-push
option toforge build
, which would skip the step of pushing to the configured repository? That way, I could runforge build --skip-push
while I am working on the project and iterating locally, and once I am ready to make my images available for deployment, I would run a regular build to push the image to ECR.Cheers!