I have a project that is set up which uses 15-20 custom add-on packages. Of which, most of them are add-on packages that I have developed to extend/modify certain features, content types, portlets, dashboards, and Web APIs.
When I have read through project provisioning and deployment documentation, it mentions Ansible playbooks, performance tuning tips, and system maintenance aspects.
What I am trying to locate is something that describes the best practices for tracking a Plone site as a git repo. I have found an unofficial .gitignore proposed @ https://github.com/buildout/buildout/blob/master/.gitignore.
So specifically should I just make the Plone/ root directory the git repo's root directory? Should I track the src/ directory? Should I track the buildout.cfg among other *.cfg files?
Also, most of the documentation covers individual add-on src structure, but is there any naming convention for the Plone directory since I might have multiple sites and cannot have multiple /my/git/server/plone.git repos. Any guidance is much appreciated. Thank you in advance!