Add-ons

You can test new or existing Plone add-ons by passing them via the PLONE_ADDONS environment variable.

The following examples adds eea.facetednavigation.

docker run -p 8080:8080 -e PLONE_ADDONS="eea.facetednavigation" plone fg

This will start your container in foreground mode and install eea.facetednavigation.

After your container started, please follow the official docs to enable the add-on in your site.

The same way as above you can pass PLONE_ZCML environment variable to include custom ZCML files or PLONE_DEVELOP environment variable to develop new or existing Plone add-ons:

docker run -p 8080:8080 \
     -e PLONE_ADDONS="plone.theme.winter" \
     -e PLONE_DEVELOP="src/plone.theme.winter" \
     -v $(pwd)/src:/plone/instance/src \
plone fg

Make sure that you have your Plone add-on code at src/plone.theme.winter and that Plone user inside Docker container (uid: 500) has the rights to read/write there:

setfacl  -R -m u:500:rwX src/
setfacl -dR -m u:500:rwX src/
getfacl src/

Running unit tests:

docker run --rm -e PLONE_ADDONS="eea.facetednavigation" \
          plone \
          bin/test -v -vv -s eea.facetednavigation

Note

Please note that passing BUILDOUT_ environment variables will slow down container creation as a buildout re-run inside container is triggered.

Thus, we strongly recommend to use this only for testing or development purpose.

For production use, create a new image as described.