curved-manchester-6600602/08/2023, 2:48 PM
makes a lot of sense to me. Most of the docs for Docker, helm, etc also follow that pattern, so following them one would end up with
and each deploy-able container "app" would be spread across 4 directories (plus tests) instead of having the Dockerfile or whatnot live right next to the source code. Is pants intentionally trying to nudge me towards that per backend layout as a best practice, or is it just an accident of the example in the docs?
enough-analyst-5443402/08/2023, 2:54 PM
and apps / projects define top-level dirs too (say
or even just
and use BUILD files there with aliases that point into the src/ trees. This allows an app / project team to maintain "links" in their app directory to all the commonly used targets spread amongst the various src/ trees in 1 convenient short-path spot.
That was the ~3rd approach all time. That was in Pants v1 though and it had more support for target aliases I think allowing you to do this. You might still be able to though.
curved-manchester-6600602/08/2023, 3:02 PM
enough-analyst-5443402/08/2023, 3:03 PM