Mautic is beautiful, free, open source marketing automation and email marketing software.
v3, v4, v3-apache, v3-fpm, v4-apache, v4-fpm, latest
Mautic is distributed under the GPL v3 license. Full details of the license can be found in the Mautic GitHub repository.
docker run --name some-mautic --link some-mysql:mysql -d mautic/mautic
The following environment variables are also honored for configuring your Mautic instance:
-e MAUTIC_DB_HOST=...(defaults to the IP and port of the linked mysql container)
-e MAUTIC_DB_USER=...(defaults to “root”)
-e MAUTIC_DB_PASSWORD=...(defaults to the value of the
MYSQL_ROOT_PASSWORDenvironment variable from the linked mysql container)
-e MAUTIC_DB_NAME=...(defaults to “mautic”)
MAUTIC_DB_NAME specified does not already exist on the given MySQL server, it will be created automatically upon startup of the mautic container, provided that the
MAUTIC_DB_USER specified has the necessary permissions to create it.
If you’d like to be able to access the instance from the host without the container’s IP, standard port mappings can be used:
docker run --name some-mautic --link some-mysql:mysql -p 8080:80 -d mautic
If you’d like to use an external database instead of a linked mysql container, specify the hostname and port with
MAUTIC_DB_HOST along with the password in
MAUTIC_DB_PASSWORD and the username in
MAUTIC_DB_USER (if it is something other than root):
docker run --name some-mautic -e MAUTIC_DB_HOST=10.1.2.3:3306 \ -e MAUTIC_DB_USER=... -e MAUTIC_DB_PASSWORD=... -d mautic/mautic
Example docker-compose.yml for mautic:
mautic: image: mautic/mautic links: - mauticdb:mysql ports: - 8080:80 mauticdb: image: mysql:5.7 environment: MYSQL_ROOT_PASSWORD: example
This image is officially supported on Docker version 1.7.1.
Support for older versions (down to 1.0) is provided on a best-effort basis.
If you have any problems with or questions about this image, please contact us through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Have you created an Integration, API Wrapper, Service, or other Tool that helps developers build on DigitalOcean? Help users find it by listing it in Community Tools.