Name: plone.docker
Owner: Plone Foundation
Description: plone on docker
Created: 2014-11-01 12:38:51.0
Updated: 2018-01-04 23:47:54.0
Pushed: 2017-09-13 13:13:12.0
Homepage: null
Size: 162
Language: Python
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Plone is a free and open source content management system built on top of the Zope application server.
Dockerfile links5.0.8, 5.0, 5, latest (5.0.8/Dockerfile)4.3.15, 4.3, 4 (4.3.15/Dockerfile)5.0.8-alpine, 5.0-alpine, 5-alpine (5.0.8/alpine/Dockerfile)4.3.15-alpine, 4.3-alpine, 4-alpine (4.3.15/alpine/Dockerfile)Make sure you have Docker installed and running for your platform. You can download Docker from https://www.docker.com.
Choose either single Plone instance or ZEO cluster.
It is inadvisable to use following configurations for production.
Plone standalone instances are best suited for testing Plone and development.
Download and start the latest Plone 5 container, based on Debian.
er run -p 8080:8080 plone
This image includes EXPOSE 8080 (the Plone port), so standard container linking will make it automatically available to the linked containers. Now you can add a Plone Site at http://localhost:8080 - default Zope user and password are admin/admin.
ZEO cluster are best suited for production setups, you will need a loadbalancer.
Start ZEO server in the background
cker run -d --name=zeo plone zeoserver
Start 2 Plone clients (also in the background)
er run -d --name=instance1 --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8081:8080 plone
er run -d --name=instance2 --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8082:8080 plone
You can also start Plone in debug mode (fg) by running
er run -p 8080:8080 plone fg
Debug mode may also be used with ZEO
er run --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8080:8080 plone fg
For more information on how to extend this image with your own custom settings, adding more add-ons, building it or mounting volumes, please refer to our documentation.
The Plone image uses several environment variable that allow to specify a more specific setup.
ADDONS - Customize Plone via Plone add-ons using this environment variableZEO_ADDRESS - This environment variable allows you to run Plone image as a ZEO client.Run Plone with ZEO and install two addons (PloneFormGen and collective.roster)
er run --name=instance1 --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8080:8080 \
DDONS="Products.PloneFormGen collective.roster" plone
PLONE_ZCML, ZCML - Include custom Plone add-ons ZCML files (former BUILDOUT_ZCML)PLONE_DEVELOP, DEVELOP - Develop new or existing Plone add-ons (former BUILDOUT_DEVELOP)ZEO_READ_ONLY - Run Plone as a read-only ZEO client. Defaults to off.ZEO_CLIENT_READ_ONLY_FALLBACK - A flag indicating whether a read-only remote storage should be acceptable as a fallback when no writable storages are available. Defaults to false.ZEO_SHARED_BLOB_DIR - Set this to on if the ZEO server and the instance have access to the same directory. Defaults to off.ZEO_STORAGE - Set the storage number of the ZEO storage. Defaults to 1.ZEO_CLIENT_CACHE_SIZE - Set the size of the ZEO client cache. Defaults to 128MB.ZEO_PACK_KEEP_OLD - Can be set to false to disable the creation of *.fs.old files before the pack is run. Defaults to true.HEALTH_CHECK_TIMEOUT - Time in seconds to wait until health check starts. Defaults to 1 second.HEALTH_CHECK_INTERVAL - Interval in seconds to check that the Zope application is still healthy. Defaults to 1 second.Full documentation for end users can be found in the “docs” folder. It is also available online at http://docs.plone.org/
If you are having issues, please let us know at https://community.plone.org
The project is licensed under the GPLv2.