With this Mautic tutorial, you will learn how to complete the Mautic 2.15.1 installation on a Virtual Private Server (VPS) with PHP 7.2 on top of Ubuntu 18.04 LTS in just about 7 minutes.
If you are a total newbie to the Linux command line, this tutorial was made specifically for you, it's the best way to get started as I carefully designed it to have the fewer amount of commands possible, so it's easier to understand and the probability of anything going sideways is minimal. It's designed to give you a quick success using the command line so you can have an easy victory and gain the confidence to later advance towards more complex, more secure and better-optimized setups.
Many companies turn to Mautic in search of a more cost-effective way to enable their organizations for the future.
Since Mautic is free to download, yeiii! One could think running it at scale could be done for free too, however, Mautic is quite a complex piece of software, and depending on your requirements, it will also need some decent hardware to run on top of. In this post, I'll give you details about the costs involved and how to source what you need.
Yeah I know, this is pretty trivial, but I had made some snapshots of the process and thought, why not? Maybe someone gets stuck in one of the steps, like the database (I did the first time I installed Mautic) So here it is...
OK so after you complete the mautic installation, you have to navigate to your server or VPS, either by using the server's IP or, if you have set up your DNS, using the domain name. After you do, and if everything went fine you will be presented with the following screens:
Mautic 3 is going to be wonderful, I have no doubt about it. The core team and the developers both from Mautic Inc and the community are simply awesome, the new paradigm proposed for Mautic 3 is wonderful and the technical possibilities are on par with the latest developments from Google. The conversation about how we are supposed to build Mautic 3 is happening right now in the #core channel of Mautic’s Slack. If you haven't paid a visit yet, this is a great moment to do so.
But there is a hidden danger lurking behind the creation of Mautic 3 and how it’s being designed at Mautic Inc, the current vision could have it’s dangers... to the community.
Please stop using Bitnami images and Cpanel / Softaculous as a quick shortcut to install Mautic.
Mautic is still a young and rapidly evolving software with frequent releases that contain new features, with new features come new bugs.
As user of Mautic self=hosted, you will need to deal with bugs, you will have to apply patches, you will have to run updates manually and you will encounter problems related to the environment in which Mautic is installed, In order to solve those issues, you will need a basic understanding of Apache or NginX, MariaDB or a compatible MySQL database, PHP configuration, and how Linux operates.
Cron jobs are supposed to be the smartest and simplest way to automate things on a Linux server, and they are to some extent. However, its design, deeply rooted on the darkest corners of the Linux kernel, designed by the deep minds that created Linux itself, doesn't always present itself as obvious to us marketers (or to any other kind of Linux Dummies), that's probably why soooo many people have issues with cron jobs. Yes, maybe this is something that should be solved within the Mautic interface, maybe someday... in the meantime, let's try to tackle this problem down, in a way even a marketer can do it :-)
There are many Mautic cron jobs you can use in your Mautic installation, but Mautic can get resource hungry over time, so you don't really want to run them all, in fact, that would be a great mistake, you only have to add the cron jobs that you actually need in your own setup, based on your own Mautic installation and the Mautic features you're currently using.
This is a guide to help you both, first discover and then choose the right Mautic cron jobs you want to deploy in order to have a perfectly smooth Mautic installation on your server.
If you are a Mautic community user or Mautic self-hosted user, chances are you are going to need help, a lot of times...
Have you noticed how some requests seem to get a lot of attention while others seem to be ignored? Some users seem to get their questions answered fast while questions from other users go unanswered forever and finally fade into oblivion.
Also, it would seem some questions get well-thought responses while others get short answers that seem not to be helpful at all.
If you are one of those guys who's questions tend to go unanswered, this post will help you get proper answers almost every time.
Every so often I get requests to deploy multi-tenant Mautic setups, those requests are usually from a Marketing agency that needs to run multiple Mautic instances for their customers or their internal usage, However, multi-tenancy is very often a misunderstood and misused concept.
Multi-tenancy is an architectural approach enabling a single instance of an application to be used by multiple organizations or users, the tenants. In multi-tenant apps, there is just one code base for everyone and the separation between clients is done in that single codebase and sustained by the database.
On the other hand, Multi-instance, what I call "Replication" provides each organization with its own codebase.
Let's analyze in detail these 2 options and find out which is the best way to run Mautic for an Agency.
Mautic can do a whole lot of smart stuff for your email, except sending it! Mautic users have to use a third party service to send emails, in this post I'll go over 3 different options for sending Mautic emails, the pros and cons of each and I'll give you a final recommendation for your business type.
There's a lot to consider when choosing the best email delivery for Mautic emails, for starters a lot of work can go into building Mautic campaigns, in those cases, the cost of sending emails will be just a small fraction of the overall spend and deliverability should be second to nothing. On the other hand, companies using Mautic to send newsletters or simpler DRIP campaigns might be more sensible to the cost of sending these emails. And finally, heavily IT bound companies might care less about pricing and will consider flexibility as the main feature to consider.
I have chosen 3 companies that will cater to each of those needs, keep reading!
Mautic will run on any server that supports PHP and a MySQL compatible database, which is little short of saying it will run anywhere, you could run it on Linux, Windows, you could run it on your phone, what the heck! you could probably run it on your smart coffee maker!
But should you? Of course not, your coffee maker runs java! hehehe.
Now seriously, which is the best platform to run Mautic? As always, it depends, so I will try to give you enough pointers for you to choose the best option for your own situation.