I’m working on bootstrapping a monorepo (my first time, fwiw) to host a legacy system that I’m porting into this monorepo.
/apps/.workspace) in /infrastructure/copilot/This worked until I upgraded to v0.4.0 a day or two ago; I could be in /infrastructure/ and run copilot svc deploy --name my-app --dockerfile ../apps/my-app/Dockerfile and the command succeeded.
After upgrading to v0.4.0, I’m getting this:
Note: It's best to run this command in the root of your workspace.
✘ Dockerfile /Users/avi/dev/my-repo/apps/my-app/Dockerfile not within workspace /Users/avi/dev/my-repo/infrastructure
I understand that the way I was using Copilot wasn’t the officially recommended way of using it, but it was working for me and I liked it.
I suspect other folks might have similar needs.
FWIW, I’ve traced this change to 6a8fa3d1f69dc417a04c1eb68b1f6d377bbc769b.
A few suggestions for the UX:
--workspace option to most CLI commands, so I could just specify the path to my workspace.copilot in its root, and the services are supposed to be in the same root. In other words, the services are supposed to be co-located with the dir copilot and it’s the combination of the two that’s a Copilot “workspace”. My preference, however, would be for that concept to evolve a bit, or perhaps we come up with a new term/concept for the dir copilot and its contents.)copilot out into the root of my monorepo, I’d prefer to name it .copilot (with the leading period character in its name)Of course I understand completely if these suggestions are declined. No worries either way.
Thank you!
🎉 thanks @huanjani !
Most helpful comment
🎉 thanks @huanjani !