Single repo for all projects
Opened this issue · 0 comments
Curious if there's been any thoughts on utilizing the top-level projects folder as the base for the git repo?
the best practices doc recommends it with a simple gitignore of the .resources directory.
Larger installs would be much simpler to integrate with git using that paradigm, as well as reducing duplication (and consolidating diffs) of exporting gateway tags in each project separately.
Note that doing this manually (i.e. without this module) using the official docker image is essentially impossible, but there is an image with slight modifications that does work to track the projects folder as a whole, but it's not always possible to re-deploy an existing system to docker. You can build via docker-compose and map a local directory to /workdir. The image then symlinks a projects folder from there that you can track changes with
The paradigm of this module works well both as a deplolyment-agnostic fresh install option as well as a drop-in solution for an existing system. Not to mention the designer controls give it a clear advantage over the manual setup of the git clone.