The cron container do not have access to the var/tmp/imports folder. so, it needs to be added / shared with both mautic_web and cron container.
Also, I think it's good to have all the mautic crons automatically be set-up, not just the 3 currently has, with a generic limits/configs, by default.
And I think usage of supervisord may backfire (just assuming), as it'll crash completely (correct me if I'm wrong) after 10 retries... and AFAIK there's no "indefinitely retry" settings in supervisord. So, if for example, I change the queue settings to sync://, the supervisord services may crash (and potentially be retried with docker-compose restart: always policy, but is that ideal?)
The
croncontainer do not have access to thevar/tmp/importsfolder. so, it needs to be added / shared with both mautic_web and cron container.Also, I think it's good to have all the mautic crons automatically be set-up, not just the 3 currently has, with a generic limits/configs, by default.
And I think usage of supervisord may backfire (just assuming), as it'll crash completely (correct me if I'm wrong) after 10 retries... and AFAIK there's no "indefinitely retry" settings in supervisord. So, if for example, I change the queue settings to
sync://, the supervisord services may crash (and potentially be retried with docker-compose restart: always policy, but is that ideal?)