This page will guide you through setting up your local environment to use and develop for Mautic.
SET GLOBAL innodb_default_row_format=DYNAMIC; SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));
cd /var/wwwif your local server root is at /var/www).
gh repo clone mautic/mautic)
composer install) if you are not using DDEV. If you're using DDEV, type
Each time you update Mautic's source after the initial setup/installation via a new checkout, download, git pull, etc; you will need to clear the cache. To do so, run the following command:
$ cd /your/mautic/directory $ php bin/console cache:clear
(Note that if you are accessing Mautic through the dev environment (via index_dev.php), you would need to add
--env=dev to the command).
composer install to ensure new vendors are installed and/or existing upgraded.
Before running these commands, please make a backup of your database.
If updating from a tagged release to a tagged release, schema changes will be included in a migrations file. To apply the changes, run
$ php bin/console doctrine:migrations:migrate
If you are updating to the latest source (remember this is alpha), first run
$ php bin/console doctrine:schema:update --dump-sql
This will list out the queries Doctrine wants to execute in order to get the schema up-to-date (no queries are actually executed). Review the queries to ensure there is nothing detrimental to your data.
If you're satisfied with the queries, execute them with
$ php bin/console doctrine:schema:update --force
Your schema should now be up-to-date with the source.
Mautic downloaded from GitHub has the development environment. You can access it by adding
index_dev.php after the Mautic URL. Eg.
http://localhost/mautic/index_dev.php/s/. Or in case of CLI commands, add
--env=dev attribute to it.
This development environment will display the PHP errors, warnings and notices directly as the output, so you don't have to open the log to see them. It will also load, for example, translations without cache, so every change you make will be visible without clearing it. The only changes which require clearing the cache are in the
In case of assets like JS, CSS, the source files are loaded instead of concatenated, minified files. This way the changes in those files will be directly visible on refresh. If you'd wanted to see the change in the production environment, you'd have to have run the
bin/console mautic:assets:generate command.
In many cases, the CSS files are built from LESS files. To compile the changes in the LESS files, run
grunt compile-less command.
In case you don't have Grunt installed firstly run
npm install -g grunt-cli to install grunt-cli globally. Then go to the Mautic root directory, and run
npm install. After that you can run the
grunt compile-less command.
Found errors? Think you can improve this documentation? edit this page