An opinionated repository for production hosting of CiviCRM on Docker (your opinions on how it could be improved are very welcome).
All images are based php-apache.
In most cases, just choose the CMS that you would like to use, e.g. civicrm:wordpress. Everything else (php version, etc.) will be set to sensible defaults. You can get more specific with one of the tags below.
WORK IN PROGRESS - USE AT YOUR OWN RISK.
These images are largely untested in production. Questions about how to use these images are very welcome in the issue queue. Answers will likely come in the form of updates to this README.md and other bits of documentation. Please share your experiences using these images so we can improve them as we go.
Implementation may well be behind the documentation for some CMS. If you are having difficulty getting going, please ping michaelmcandrew in the CiviCRM docker chat channel here: https://chat.civicrm.org/civicrm/channels/docker and I will try and help, else feel free to create and issue.
The following tags are available:
5.69.5-drupal-php8.05.69-drupal-php8.05-drupal-php8.0drupal-php8.0(5/drupal/php8.0)5.69.5-drupal-php8.15.69-drupal-php8.15-drupal-php8.15.69.5-drupal5.69-drupal5-drupaldrupal-php8.1drupal(5/drupal/php8.1)5.69.5-drupal-php8.25.69-drupal-php8.25-drupal-php8.2drupal-php8.2(5/drupal/php8.2)5.69.5-drupal-php8.35.69-drupal-php8.35-drupal-php8.3drupal-php8.3(5/drupal/php8.3)5.69.5-wordpress-php8.05.69-wordpress-php8.05-wordpress-php8.05.69.5-php8.05.69-php8.05-php8.0wordpress-php8.0php8.0(5/wordpress/php8.0)5.69.5-wordpress-php8.15.69-wordpress-php8.15-wordpress-php8.15.69.5-wordpress5.69-wordpress5-wordpress5.69.5-php8.15.69-php8.15-php8.15.69.55.695wordpress-php8.1wordpressphp8.1latest(5/wordpress/php8.1)5.69.5-wordpress-php8.25.69-wordpress-php8.25-wordpress-php8.25.69.5-php8.25.69-php8.25-php8.2wordpress-php8.2php8.2(5/wordpress/php8.2)5.69.5-wordpress-php8.35.69-wordpress-php8.35-wordpress-php8.35.69.5-php8.35.69-php8.35-php8.3wordpress-php8.3php8.3(5/wordpress/php8.3)
There are a couple of options for getting started. Here are a couple of common workflows that I use.
If I plan on doing a fair amount of custom development as part of a project, I like to start with a 'mono repo' on the host machine containing everything from the CMS root downwards (excluding files with credentials in and folders that include uploads via the web server). This makes working with IDEs, debugging, etc. easier.
If you aren't planning on doing much custom development (e.g. maybe you are just installing already existing modules and extensions) it might make more sense to take advantage of the CMS and CiviCRM already installed on the image (at /var/www/html).
To get a local project up and running, choose your CMS flavour from the docker-compose and copy the entire directory to somewhere like ~/projects/backdrop-example-project
- Copy the
dev.dist.envfile to.env. and edit as appropriate (choose sensible passwords, set the base url and other required environment variables, e.g. the domain you want the site to be available at. - Copy
docker-compose.dev.dist.ymltodocker-compose.ymland assign port numbers as appropriate (see Reverse proxies for more details). - If you are mounting a mono repo from the host to the container (see above), place it in the
srcfolder, and uncomment the./src:/var/www/htmlvolume. - If you want development site to be available at a memorable address and/or you want to serve it via https, configure it now.
- Run
docker-compose up -d - Install a new site with something like
docker-compose exec civicrm civicrm-docker-install.
Note that if you already have a dump containing the database and file dump (in the format expected by civicrm-docker) you do not need to install the CMS and CiviCRM. You can just initialise it with docker-compose exec civicrm civicrm-docker-install and then follow the load instructions below.
Running docker-compose exec civicrm civicrm-docker-dump will place a database and file dump in the /state folder of the container (which is mapped to the ./state sub-folder in your docker-compose root on the host).
Running docker-compose exec civicrm civicrm-docker-load will load an existing database dump from the /state folder of the container (which is mapped to the ./state sub-folder in your docker-compose root on the host.
The images are designed to be used with whatever MySQL backend you like: one in a container, one on bare metal, or maybe a DB appliance from a cloud provider.
A simple mysql image based on the official mysql:8.0 and suitable for CiviCRM can be found at michaelmcandrew/mysql-civicrm. See the docker-compose.dev.dist.yml files in the docker-compose directory for an example of this image in use.
For convenience, a zip of the original source code of CiviCRM and the selected CMS can* be found at /usr/local/src.
*Not quite ready yet!
To update the images on Docker Hub that are defined in this repository, run the following script:
./update.pyThis calls the following processes in order:
generate.pyautomates the generation of Dockerfiles (updates combos.json).build.pybuilds images based on the dockerfiles (based on combos.json).publish.pypublishes these images on dockerhub (based on combos.json).