ofelia VS deck-chores

Cron jobs are an essential part of maintaining modern applications, automating tasks like data fetching, report generation, and updates. But when you're running containerized apps in Docker, traditional cron setups don’t work seamlessly. Enter Docker Ofelia, a simple and effective solution to run cron jobs in a containerized environment.

To anybody that is familiar with Ofelia: how do you use different log files for different jobs?

I've been trying to figure out how to run cron jobs in my docker containers. Most of the solutions I see are some version of "make a separate container to run your crons". One version of this solution is ofelia, which people seem to like a lot.

If you want to run periodic commands on your containers, have you considered using a cron replacement (ofelia chadburn or maybe docker-crontab?

I found Ofelia but from the quick glance I took at their documentation it seems it don't allow to set scheduling rules from the docker compose.

I'm in the exact same situation. I'm currently trying to get mcuadros/ofelia installed to run as a scheduler within Docker. Here's a sample file for Ofelia to run the photoprism import (jobs.ini): https://dl.photoprism.org/docker/scheduler/

Not exactly using the OS' crontab but if you're using Docker to deploy your Django, you might actually find it cleaner to use something like Ofelia to run commands in your Django container.

If you'd like to have this schedule as part of your docker setup as well look into Ofelia https://github.com/mcuadros/ofelia You can run commands - local (on the host or on the docker container Ofelia runs in - by 'docker exec' in an existing container - by spinning up a new container

# See https://github.com/mcuadros/ofelia/blob/master/docs/jobs.md for job settings!

I'm trying to push some Information to an API on a scheduled basis. I figured ofelia is exactly what I need. A Test with "echo test" as command worked just fine, I could see the output in the logs.No if I try to run a curl command I get the following error:2022-01-27T11:30:09.008Z common.go:121 ▶ ERROR [Job "dyndns-kasm" (b5d84c412e5f)] Finished in "1.014721ms", failed: true, skipped: false, error: exec: "curl": executable file not found in $PATH

I would use deck-chores for this: https://github.com/funkyfuture/deck-chores

run a 'deck-chores' container on the local host: https://github.com/funkyfuture/deck-chores This gives you a docker 'aware' cron driven directly by container labels