I toke some time to find the docs about the custom buildout github configuration. I think it would be good to have a link to the docs on custom_playbook.rst, also I could make a merge request but didn't figure out how to cross reference the docs. I think it could be something like this:
If you choose the git repository strategy, your buildout skeleton must, at a minimum, include bootstrap.py and buildout.cfg files. It will also commonly contain a src/ subdirectory and extra configuration files. It will probably not contain bin/, var/ or parts/ directories. Those will typically be excluded in your .gitignore file.
To do this, you might have to configure the :ref:plone_buildout_git_repo <plone_buildout_git_repo> variable.
If you use a buildout directory checkout, you must still specify in your Playbook variables the names and listening port numbers of any client parts you wish included in the load balancer configuration. Also specify the name of your ZEO server part if it is not zeoserver.
I toke some time to find the docs about the custom buildout github configuration. I think it would be good to have a link to the docs on custom_playbook.rst, also I could make a merge request but didn't figure out how to cross reference the docs. I think it could be something like this:
If you choose the git repository strategy, your buildout skeleton must, at a minimum, include
bootstrap.pyandbuildout.cfgfiles. It will also commonly contain asrc/subdirectory and extra configuration files. It will probably not containbin/,var/orparts/directories. Those will typically be excluded in your.gitignorefile.To do this, you might have to configure the :ref:
plone_buildout_git_repo <plone_buildout_git_repo>variable.If you use a buildout directory checkout, you must still specify in your Playbook variables the names and listening port numbers of any client parts you wish included in the load balancer configuration. Also specify the name of your ZEO server part if it is not
zeoserver.