Shipped a Mautic 7.2.2 one-click Railway template — in-container cron was the hard part

I needed a self-hosted marketing automation stack that didn't lock me into a SaaS tier, and Mautic is the open-source answer — but its deployment story is rough. The official Docker setup expects you to wire up cron externally, manage a separate MySQL instance, and manually create the first admin user after install. I wanted something an operator could spin up in one click and actually use without reading three wiki pages.
The concrete detail that took the longest to get right was moving cron inside the application container. Mautic hammers its task queue during campaign sends, and external cron jobs kept drifting out of sync with the container's filesystem. Now the container runs its own scheduler via a lightweight entrypoint that loops php bin/console mautic:cron:run on an interval, so campaigns, email queues, and maintenance tasks stay atomic with the app code. MySQL 8 runs as a service in the same Railway project, and the admin user auto-seeds on first boot with credentials printed to the deploy logs.
What it costs the operator is compute headroom. Mautic isn't a lightweight PHP app — during a broadcast to a few thousand contacts, the cron worker spikes CPU and the queue depth becomes the bottleneck. You're paying for a container that sits mostly idle but needs to burst hard when a campaign fires. I ended up packaging the whole thing as https://github.com/INAPP-Mobile/mautic so others can fork the Railway config and see the cron setup themselves.