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.
Several weeks ago it was announced on the #core channel, that Mautic 3 development teams where being formed. I was very excited, naturally. I took a look at how the groups where setup and I noticed one thing, this was a purely technical and completely development focused set of groups, where was the "Product Side" going to be discussed, I wondered... So I asked this very specific question during the next #core meeting... "Are Mautic 3 development groups going to define what Mautic 3 as a product will be like?"
The answer I received was as clear as it was troubling: "Mautic 3 will follow the vision DB Hurley has already defined"
You know what NTFS is, that's your windows file system, right? You probably also know that Linux uses several different file systems, the most extended one being ext4...
Here's the thing.... there's an old file system called ZFS, originally designed by SUN Microsystems in 2001 and delivered for the first time as a Solaris product on 2005. At the time, it was a very specific tool designed to serve the needs of a reduced number of companies running large pools of disks sitting in a server room.
What happened between then and now we all know, the Internet became mainstream, allowed cloud computing, then DevOps emerged and then containers exploded; as a consequence of those changes, the needs of system administrators and users alike have completely changed. What used to be a strange and relatively complex file system, tailored for very specific needs and used exclusively by just a few people, might be the best option nowadays and because it was so well architected, 15 years after it's now shining more than ever, rapidly growing in adoption and menacing to become mainstream.
A few months ago, one of our fellow Mauticians just made an interesting remark on Mautic's #General Slack channel:
Mautic is a box o' bugs: Anyone know a stable release of mautic? *most stable (bc apparently nothing is stable) went thru 2.11.0, 2.12.2, 2.13.1 --> no dice in one release test emails are breaking, in another campaigns don't work, and in another you cannot even save the config page, it's like a whole new box o' bugs with each release.
There's much more to making backups than just copying files, as you probably know, you need a backup strategy. In this post, I'm not going to enter in detail on the strategic part. Anyway, I'm going to abide by the most basic and indispensable elements of a backup strategy, that is so, if you ever need your data, you have a certain guarantee that your data will remain available to you when most needed.
I'm going to start with a little bit of theory, I know it's boring, but it will let you understand what you're doing in the second part when we start using the console and giving instructions to the server.
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.
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 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.
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.
On the other hand, if you are more experienced with Linux, and don't mind some extra complexity, this might be a better tutorial for you: Securing your Mautic Installation
Installing Mautic plugins or Mautic Mixins (as only God knows why they are officially named now) is really simple... most of the time... But there's always some obscure unofficial plugin that you really need so badly, and those always have little or no instructions and hence they refuse to install.
Don't worry, it really is very simple, if you know a couple of tricks... Let's start with the basics:
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 :-)