Mautic is a great tool; I hope if you're here, you already knew that. Either way, this repository is for anyone wanting to harness the power of Mautic, pretty much anywhere; without a hiccup or delay and crave a 'right here, right now' type-solution to their dreams of becoming the next 'over-night millionaire.' Just kidding...(but seriously while this tool won't make you millions over-night, it will help to get you moving the right direction.)
I (@ran-dall) started this project as started as an effort to help new and existing Mautic users set up a Mautic instance on different cloud providers and their local machines for testing/demonstration purposes.
These set-ups are not intended to follow all of what may be considered best-practices by your specific cloud provider, but the effort is made to follow Vagrant best-practices. Sometimes those efforts are hindered by the capabilities of the plugins available for the specific cloud provider.
Below you'll find the revalant notes and caveats for each set-up.
Note: Currently, this project only supports setting up in a local-environment on Virutal-Box. However, I intend to add more providers soon.
- I pull the
debian/contrib-stretch64box to avoid any potentialnfsproblems. You could switch this back todebian/stretch64if you'd like; but if you do, it would recommend you also install thevagrant-vbguestto make sure there are no hiccups with your instance's installation. You could also probably switch this to some otherDebian 9based box, but your mileage may vary.
- To create the
MariaDBdatabase needed by Mautic, you need to supply a database name (DBNAME), host (DBHOST), user (DBUSER), and password (DBPASSWD). All the requiredvariableshave already set for you in the provisioning script as follows, feel free to change the values as you see fit (and you know what you're doing).DBHOST=localhostDBNAME=mauticdbDBUSER=mauticuserDBPASSWD=mauticpwd
-
Basic
SSLhas been implemented forlocalhostto fullfill the miniumum deployment requirements. Accesshttps://to bypass any Mautic installation warnings.Clone repo and run
vagrant upin project root directory.