Sorry for the delay in responding. Still putting my ideas together.
We recently deployed two customer plone sites using docker. We had to do a lot of reading and figuring out.
The idea is to “bundle” the best practices and knowledge into a plonecli command.
It would be based on plone.docker and most likely make use of docker compose.
A developer would be able to use the plonecli to bootstrap and manage docker based development and deployment.
Imagine being able to enter a buildout folder and type:
the resulting output might look like this:
Your buildout has been dockerized.
It is now possible to launch your Plone site on any docker ready
server using the following command:
docker-compose up -d
You can also deploy your Plone site to platforms that support docker, such as:
"heroku, platform.sh and elastic beanstalk"
In case there are copyright issues we could use a command like
This will require a lot more ground work before it is ready for plonecli. This work will have to at least include the following:
- A docker ready buildout template file (maybe called it
docker.cfg). This is needed because the standard buildout.cfg has too many “extras” that don’t play well with plone.docker.
- a useful docker-compose.yml file
- sensible defaults for integrating with Continuous Delivery (gitlab is an easy target for this).
Stuff I’m looking at as examples or references: