New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dockerized Development Misses The Vendor Folder #1259
Comments
Seems to be duplicated from #1242 |
Potentially :) this one is more concerned with making sure our CI/CD pipeline caches the GOPATH (or rebuilds with a public proxy) |
Hey, I'm new here and still getting familiar with the system. This one looks like something I can start working on. |
@keremgocen sounds good ✌️ |
@keremgocen would you still be interested in taking this one? I'm happy to help out if you are. If not, absolutely no worries. I just wanted to check in. |
@arschles feel free to take it, I recently started a new project so it's a bit hard for me to create extra time right now. I'm sure I can find something else to work on when I have a better schedule. |
Just so I understand you right with this one @marwan-at-work (it's rather late here): Are you wanting the developer environment in docker-compose to be able to Or You want to migrate Or something completely different? 🤷♂😅 P.S Excuse the crude examples |
This seems obsolete by now, no |
Our
docker-compose up dev
command uses the same Dockerfile we use in our deployment pipeline which includes-mod=vendor
...However, our deployment pipeline runsgo mod vendor
on the fly while our development environment doesn'tWe therefore should expose the local cache to our Dockerfile build in our pipeline so that we can remove the
-mod=vendor
and also ensure that we don't re-download everything when building docker.The text was updated successfully, but these errors were encountered: