Cronjobs

[josaur]

Hey there,
how do I configure the cronjobs for Civi in docker in comparison to other deployments? Couldn't find anything in the docs for that.

Greetings
josaur

[michaelmcandrew]

We don't have an opinion on that. The standard way to run cron is cv api job.execute, which is what I would recommend but how that gets executed is currently out of scope. https://docs.civicrm.org/sysadmin/en/latest/setup/jobs/

Not averse to including something but also don't want to dictate a way of doing it if people want to have flexibility.

[josaur]

Thanks for the answer. I thought about implementing the cronjob configurable via ENV on Docker Level, which uses crontab or something else in side the container. In other setups I as well would trigger this by a sidecar container or use an second container for executing asyncronos jobs. From my perspective execting the cronjob inside the running container would be the most basic approach for having an out of the box working deployment without the need of further configurations.

[michaelmcandrew]

I looked again and realised that cron is already installed on the PHP container :)

There is another issue that we'd need to deal with though - CivICRM requires that you specify a user to run the cron job and given that users are install specific, we'd either need to enforce a convention or ensure that we specify the correct user via a $CRON_USER environment variable.

If we go with the variable route, we could default it to admin or UID 1 or similar.

Or we could use the presence of this variable to decide whether to fire the cron.

To be honest, I am not sure why we need to specify the user to run cron in CiviCRM. It would be good to have that discussion but it is probably out of scope of this issue. But it would be nice to be able to eliminate that requirement if possible.

Another approach would be to add a $CRON_USER CiviCRM settings and add a cv cron command that looks up that user. That would be generally useful for the project and not just for docker. @totten @ufundo - you might have thoughts on this.

[michaelmcandrew]

For what it is worth, we now have a cv core:cron command so this is one step closer now. See civicrm/cv#254.

[josaur]

Hi Sounds Great thanks for the information 👍

[stakaz]

Hello, while the issue is still open, is there a working solution to setup cron for civicrm standalone in the docker container? It would be possible for me to build the image myself, if the setup is possible this way.

Thanks

[josaur]

Yes I do have an version in my fork, which I'm currently testing and than contributing back. It contains furthermore an helmchart for k8s deployment and an civi-drupal version in docker. Within this version it runs backed cronjobs into the container if the ENV is set
https://github.com/josaur/civicrm-docker