Skip to content

Latest commit

 

History

History
60 lines (39 loc) · 1.87 KB

README.md

File metadata and controls

60 lines (39 loc) · 1.87 KB
Raw

BME customized mautic docker image

See the original README here.

This image e.g. installs the AWS SES plugin. Check the latest commits to see what docker image level custom modifications we have.

Patches

Be My Eyes Mautic is patched in two ways:

  • By editing the Dockerfiles (apache and fpm) in this repository.
  • By Editing Mautic source code with patch files. These patch files are applied during the image build phase.

Why old style patch files are used instead of making a local bme fork of the mautic git repository?

When the patches are kept minimal they most likely apply to future versions of Mautic too. This means updating Mautic doesn't become hard. With patch files it can be still done by just changing the MAUTIC_VERSION in the dockerfile.

How to produce a new source code patch

  • Download the current Mautic open source version from GitHub.
  • Make changes
  • Commit you changes
  • Run git format-patch -1 HEAD
  • Copy the resulted patch file to /bme-patches directory
  • Add patch -s -p1 < /bme-patches/0001-new-patch.patch line after the existing patch command to both Dockerfiles

Releasing a new Docker image

Login (if necessary):

$ az login
$ az acr login --name bmeimageregistry

Build the image:

$ docker buildx build --platform linux/amd64 -f apache/Dockerfile -t bmeimageregistry.azurecr.io/bme-mautic .

If the build fails, try to give Docker at least 8GB RAM.

Push the image:

$ docker push bmeimageregistry.azurecr.io/bme-mautic

Image is used from Mautic Kubernetes configuration in https://github.com/bemyeyes/k8s-cluster

To take the new image into use:

kubectl -n mautic rollout restart deployment mautic-web
kubectl -n mautic rollout restart deployment mautic-cron
kubectl -n mautic rollout restart deployment mautic-worker

(Image pull policy is set to always so this is enough)