During app deployment on clusters, we need to make sure the *.service files have access to the Dockerfiles and any other resources they need. We provide access via the git repository on the hook server.
However, it is a little clumsy to clone the entire repository when we only need the contents of a single "launch" sub-directory. Explore of the use of "sparse" git clones that allow selective cloning to be more graceful.
During app deployment on clusters, we need to make sure the *.service files have access to the Dockerfiles and any other resources they need. We provide access via the git repository on the hook server.
However, it is a little clumsy to clone the entire repository when we only need the contents of a single "launch" sub-directory. Explore of the use of "sparse" git clones that allow selective cloning to be more graceful.