Nuevo Componente: Programador

I have a collection of Symfony console commands that I would like to run using the scheduler at different times but I would like to be able to manage these commands and their CRON expression from the database.

So I have created a `ScheduledCommand ' entity with properties such as

• id,
• command e.g. app:send-api-create,
• schedule e.g. */5 * * * *, and
• enabled, e.g. true or false

I manage these ScheduledCommands objects from the UI.

Then I have the Schedule.php, what would be the best way to update the scheduler in real-time, for instance, if the command is changed (arguments/options updated) or the CRON expression is altered in the database, it also reflects in the scheduler and consumer picks up the new changes in real time?

Currently, if I have the consumer running in the terminal and any command is changed from the UI, it won't be reflected in the consumer.

bin/console messenger:consume scheduler_default -vv

public function getSchedule(): SymfonySchedule
{
	$schedule = new SymfonySchedule();
        $commands = $this->scheduledCommandRepository->findAll();
        foreach ($commands as $command) {
            $message = new RunCommandMessage($command->getCommand());
            $this->recurringMessages[$command->getId()] = RecurringMessage::cron($command->getSchedule(), $message);
        }

        if (empty($this->recurringMessages)) {
            return $schedule;
        }

        return $schedule->with(...$this->recurringMessages);
    }
}

Does anybody know how to deploy a symfony app with scheduler on azure? I have an ASP with a PHP webapp on azure. I think best practice would be to use a docker image instead?

If so, which docker image would you recommend for production?

Is this correct?

"Previously, Symfony had separate commands for processing scheduled tasks and regular messages:

•	scheduler:consume for scheduled tasks 
•	messenger:consume for regular messages

These processes operated independently, requiring separate execution to handle both scheduled and regular messages. 

In Symfony 7.2, the Scheduler has been fully integrated into the Messenger system. Scheduled tasks are now treated as Messenger messages, eliminating the need for a separate scheduler:consume command. Instead, the messenger:consume command processes both regular and scheduled messages.

Therefore, to process scheduled tasks in Symfony 7.2, you should use the messenger:consume command with the appropriate transport:
php bin/console messenger:consume async -vv

This command will handle both regular and scheduled messages, streamlining the message processing workflow."

I use to clear cache every time I push changes. It affects the scheduler cache? clear cache with cache:clear after pushing changes is not a good practice?

In the documentation they use "(new Schedule())->with()", but here you are using "(new Schedule())->add()".
Why?

Hello,
I don't get one thing...
I've created a scheduler, which executes every 7 seconds (I don't add any lock, as you can see):

public function getSchedule(): Schedule
{
        return (new Schedule())->add(
            RecurringMessage::every('7 seconds', new RetrievePushCampaignMessage),
        )->stateful($this->cache);
}

This scheduler sometimes runs very hard tasks (> 7 seconds), and it looks like next scheduler tick isn't triggered until previous tick isn't finished. If some scheduler tick executes, let's say, 2 minutes, there is no next scheduler ticks (every 7 seconds) during those 2 minutes.

I expected, that scheduler starts some task and handles it in background, so "7 seconds" works like a clock (like unix cron). But it looks like some blocking process is present, and next scheduler ticks "waiting" for previous task finishing.

Am I right or I miss something?

PS. Just in case - here are my scheduler process settings (in supervisor conf):

[supervisord]
directory = /app/

;/etc/supervisor/conf.d/scheduler-default-worker.conf
[program:messenger-consume]
user=myuser
command=php /app/bin/console messenger:consume scheduler_default
numprocs=1
startsecs=0
autostart=true
autorestart=true
startretries=50
process_name=%(program_name)s_%(process_num)02d
stopsignal=KILL
stopasgroup=true

Is it good to use this component for database and/or images upload daily backups?