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
fix(deploy): use paths relative to analyzed dir, not project root
When user specifies path="services/foo" to deploy a subdirectory, the
dockerfile paths should be relative to THAT directory, not the project root.
This matches the manual wizard behavior when you run `sync-ctl deploy`
from within the service directory:
- dockerfile: "Dockerfile"
- context: "."
The GitHub repo structure may differ from the local filesystem structure.
For example, locally you might have:
/project/services/contact-intelligence/Dockerfile
But the GitHub repo might have:
/Dockerfile (at root)
Previously we were prepending args.path to make paths "repo-root-relative",
but this broke deployments when the repo structure differed from local.
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments