My approach of developing a customer addon is to setup a deployment plone buildout and develop my addon in the src/
folder. This then looks something like this:
[buildout]
extends =
http://dist.plone.org/release/5.1-latest/versions.cfg
find-links =
http://dist.plone.org/release/5.1-latest/
http://dist.plone.org/thirdparty/
extensions =
mr.developer
parts =
instance
sources = sources
sources-dir = src
auto-checkout =
my.addon
[sources]
my.addon = git git@myrepo.gitlab.com:company/my.addon
[instance]
recipe = plone.recipe.zope2instance
user = admin:admin
http-address = localhost:8080
debug-mode = on
verbose-security = on
eggs =
Plone
my.addon
with this approach you can simply add other addons in the [sources]
section and add them either to your setup.py
install_requires or your [instance]
eggs ...