Mailwizz 2 in docker

[jsrhodes15]

Hello,

I recently purchased a mailwizz license, and I intend on hosting on Fly.io. To do this, I need to run mailwizz in a docker container, without docker-compose. I can't seem to find anyone (or any discussions regarding) doing it this way. I have a mariadb database setup, and now I just need a valid Dockerfile which contains all of the necessary dependencies.

I see that you are thinking about providing Docker for v3, but I don't know when that will be. Any help would be awesome!

 

[twisted1919]

You just need nginx and php in for docker compose, there are many resources to help you add this, things like chatgpt could literally generate it for you in seconds, this is pretty much the reason we don't provide one.

 

[jsrhodes15]

Hey, thanks so much for the quick reply.

You're right that ChatGPT can generate a starting point, but I want to be honest about how that actually played out. I spent about 7 hours—hands on keyboard—going back and forth with ChatGPT to get everything configured properly. I use ChatGPT daily and have solid experience with Docker, Linux, crons, PHP, and email marketing tools (I have used Mautic several times in the past), so I didn’t come at this as a total beginner.

The issues I ran into included missing dependencies, incorrect flags during installation, file permission problems—you name it. I did eventually get MailWizz running smoothly on Fly.io (which I’m familiar with), and it’s working great now.

That said, I have to admit, I found the tone of your reply a bit dismissive. I fully understand the support burden you’re trying to avoid, and I deeply appreciate the work that’s gone into MailWizz—there’s nothing else with this quality (fantastic) and at this price point (more than fair) that even comes close. My intention isn’t to give you a hard time; rather, I just want to highlight that the process is more involved than it may seem on the surface, even for experienced users.

Also, since you’ve mentioned plans to offer an official Docker setup, I figured you might already have something more refined internally—something that would save both your team and users a lot of duplicated effort.

Thanks again for your work and for taking the time to reply.

P.S. I am happy to share what I ended up doing if this helps anyone in the future. I am not going to put the code itself up on github, because I fully respect the work being done here, but I can create a gist or something of the pertinent Dockerfile(s) and various supporting files.