docker
ability to check out multiple repos to the dev container
Tell us about your request A clear and concise description of what you want to happen or the change you would like to see
Which service(s) is this request for? Let us know which product(s) you want this for?
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Are you currently working around the issue? A clear and concise description of any alternative solutions or features you've considered or are using today.
Additional context Add any other context or screenshots about the feature request here.
Hey @torstenek could you explain a bit more what you are after and what is your usecase?
Thanks
@rumpl I think this is a similar concept to what I am looking for so I will hijack but please let me know if I need to get booted to my own issue.
The setup we run is each microservice is in its own repo (product-a-front-end, product-a-backend, product-b-front-end, etc) then we have another repo (dev-infrastructure or something like that) that containers various "project" folders. Each with a compose file and maybe database seeds, nginx configs, etc for that project.
What we need here is the ability to link all that up somehow. I realize this is not an easy UI problem to solve, but having a way to orchestrate multiple repos together would allow us to do this. We simply didn't want to do the mega mono-repo route as the commit noise and CI targeting was just not worth the effort. Just found this easier for us.
Maybe this requires another file, separate from docker-compose, that contains the metadata needed to clone/pull multiple repos into a single folder?
An umbrella repo holding each service as a git submodule worked as a stopgap for me.
On Tue, 13 Jul 2021 at 02:28, Ross Gerbasi @.***> wrote:
@rumpl https://github.com/rumpl I think this is a similar concept to what I am looking for so I will hijack but please let me know if I need to get booted to my own issue.
The setup we run is each microservice is in its own repo (product-a-front-end, product-a-backend, product-b-front-end, etc) then we have another repo (dev-infrastructure or something like that) that containers various "project" folders. Each with a compose file and maybe database seeds, nginx configs, etc for that project.
What we need here is the ability to link all that up somehow. I realize this is not an easy UI problem to solve, but having a way to orchestrate multiple repos together would allow us to do this. We simply didn't want to do the mega mono-repo route as the commit noise and CI targeting was just not worth the effort. Just found this easier for us.
Maybe this requires another file, separate from docker-compose, that contains the metadata needed to clone/pull multiple repos into a single folder?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker/dev-environments/issues/19#issuecomment-878685784, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABKUWMQ4DF2SZMDI6Q4WPDTXOCBXANCNFSM47T5KFCQ .
My scenario is a git submodule inside the main repository that was cloned by docker dev enviroment, what I would like is for it to clone the submodules as well (git submodule update --init)
I'm also trying to achieve this with submodules. I can create a new dev container from the wrapping repo. As the repo is private I cannot run git submodule update --init. Result is [email protected]: Permission denied (publickey). error.
I fixed my issue by using ssh-agent instead of a ssh config file and then creating a container with git ssh instead of git https.