Download the PHP package eurotolia/mastercron without Composer

Crunz

Install a cron job once and for all, manage the rest from the code.

Crunz is a framework-agnostic package to schedule periodic tasks (cron jobs) in PHP using a fluent API.

Crunz is capable of executing any kind of executable command as well as PHP closures.

Version	Supported PHP versions
dev v3 (v3.2-dev)
stable v3 (v3.1.0)
stable v2 (v2.3.1)
stable v1 (v1.12.4)

Roadmap

Installation

To install it:

If the installation is successful, a command-line utility named crunz is symlinked to the vendor/bin directory of your project.

How It Works?

The idea is very simple: instead of installing cron jobs in a crontab file, we define them in one or several PHP files, by using the Crunz interface.

Here's a basic example:

To run the tasks, you only need to install an ordinary cron job (a crontab entry) which runs every minute, and delegates the responsibility to Crunz' event runner:

The command schedule:run is responsible for collecting all the PHP task files and run the tasks which are due.

Task Files

Task files resemble crontab files. Just like crontab files they can contain one or more tasks.

Normally we create our task files in the tasks/ directory within the project's root directory.

By default, Crunz assumes all the task files reside in the tasks/ directory within the project's root directory.

There are two ways to specify the source directory: 1) Configuration file 2) As a parameter to the event runner command.

We can explicitly set the source path by passing it to the event runner as a parameter:

Creating a Simple Task

In the terminal, change the directory to your project's root directory and run the following commands:

Then, add a task as below:

There are some conventions for creating a task file, which you need to follow. First of all, the filename should end with Tasks.php unless we change this via the configuration settings.

In addition to that, we must return the instance of Schedule class at the end of each file, otherwise, all the tasks inside the file will be skipped by the event runner.

Since Crunz scans the tasks directory recursively, we can either put all the tasks in one file or across different files (or directories) based on their usage. This behavior helps us have a well organized tasks directory.

The Command

We can run any command or script by using run(). This method accepts two arguments: the command to be executed, and the command options (as an associative array) if there's any.

Normal Command or Script

In the above example, --destination is an option supported by backup.php script.

Closures

We can also write to a closure instead of a command:

Frequency of Execution

There are a variety of ways to specify when and how often a task should run. We can combine these methods together to get our desired frequencies.

Units of Time

There are a group of methods which specify a unit of time (bigger than minute) as frequency. They usually end with ly suffix, as in hourly(), daily(), weekly, monthly(), quarterly(), and yearly .

All the events scheduled with this set of methods happen at the beginning of that time unit. For example weekly() will run the event on Sundays, and monthly() will run on the first day of each month.

The task below will run daily at midnight (start of the daily time period).

Here's another one, which runs on the first day of each month.

Running Events at Certain Times

To schedule a one-off tasks, you may use on() method like this:

The above task will run on the first of march 2016 at 01:30 pm.

On() accepts any date format parsed by PHP's strtotime function.

To specify the time of a task we use at() method:

If we only pass a time to the on() method, it will have the same effect as using at()

We can combine the "Unit of Time" methods eg. daily(), monthly() with the at() or on() constraint in a single statement if we wish.

The following task will be run every hour at the 15th minute

hourlyOn('15') could have been used instead of hourlyAt('15') with the same result

The following task will be run Monday at 13:30

Sunday is considered day 0 of the week.

If we wished for the task to run on Tuesday (day 2 of the week) at 09:00 we would have used:

Task Life Time

In a crontab entry, we can not easily specify a task's lifetime (the period of time when the task is active). However, it's been made easy in Crunz:

Or alternatively we can use the between() method to accomplish the same result:

If we don't specify the date portion, the task will be active every day but only within the specified duration:

The above task runs every five minutes between 12:30 pm and 4:55 pm every day.

An example of restricting a task from running only during a certain range of minutes each hour can be achieved as follows:

The above task runs every hour between minutes 5 to 15

Weekdays

Crunz also provides a set of methods which specify a certain day in the week.

• mondays()
• tuesdays()
• ...
• sundays()
• weekedays()
• weekends()

These methods have been designed to be used as a constraint and should not be used alone. The reason is that weekday methods just modify the Day of Week field of a cron job expression.

Consider the following example:

At first glance, the task seems to run every Monday, but since it only modifies the "day of week" field of the cron job expression, the task runs every minute on Mondays.

This is the correct way of using weekday methods:

(An easier to read alternative with a similar result ->weeklyOn(0,'13:30') to that shown in a previously example above)

The Classic Way

We can also do the scheduling the old way, just like we do in a crontab file:

Setting Individual Fields

Crunz's methods are not limited to the ready-made methods explained. We can also set individual fields to compose custom frequencies similar to how a classic crontab would composed them. These methods either accept an array of values, or list arguments separated by commas:

Or:

Based on our use cases, we can choose and combine the proper set of methods, which are easier to use.

Running Conditions

Another thing that we cannot do very easily in a traditional crontab file is to make conditions for running the tasks. This has been made easy by when() and skip() methods.

Consider the following code:

Method when() accepts a callback, which must return TRUE for the task to run. This is really useful when we need to check our resources before performing a resource-hungry task.

We can also skip a task under certain conditions, by using skip() method. If the passed callback returns TRUE, the task will be skipped.

We can use these methods several times for a single task. They are evaluated sequentially.

Changing Directories

You can use the in() method to change directory before running a command:

Parallelism and the Locking Mechanism

Crunz runs the scheduled events in parallel (in separate processes), so all the events which have the same frequency of execution, will run at the same time asynchronously. To achieve this, Crunz utilizes the symfony/Process library for running the tasks in sub-processes.

If the execution of a task lasts until the next interval or even beyond that, we say that the same instances of a task are overlapping. In some cases, this is a not a problem. But there are times, when these tasks are modifying database data or files, which might cause unexpected behaviors, or even data loss.

To prevent critical tasks from overlapping each other, Crunz provides a locking mechanism through preventOverlapping() method, which, ensures no task runs if the previous instance is already running.

By default, crunz uses file based locking (if no parameters are passed to preventOverlapping). For alternative lock mechanisms, crunz uses the symfony/lock component that provides lock mechanisms with various stores. To use this component, you can pass a store to the preventOverlapping() method. In the following example, the file based FlockStore is used to provide an alternative lock file path.

As of Symfony 5.0 the StoreInterface has been split into BlockingStoreInterface and PersistingStoreInterface. To use any of the persistent locks (Redis, PDO, etc) they need to be decorated by the RetryTillSaveStore.

Keeping the Output

Cron jobs usually have outputs, which is normally emailed to the owner of the crontab file, or the user(s) set by the MAILTO environment variable inside the crontab file.

We can also redirect the standard output to a physical file using > or >> operators:

This kind of output logging has been automated in Crunz. To automatically send each event's output to a log file, we can set log_output and output_log_file options in the configuration file accordingly:

This will send the events' output (if executed successfully) to /var/log/crunz.log file. However, we need to make sure we are permitted to write to the respective file.

If we need to log the outputs on an event-basis, we can use appendOutputTo() or sendOutputTo() methods like this:

Method appendOutputTo() appends the output to the specified file. To override the log file with new data after each run, we use saveOutputTo() method.

It is also possible to send the errors as emails to a group of recipients by setting email_output and mailer settings in the configuration file.

Error Handling

Crunz makes error handling easy by logging and also allowing you add a set of callbacks in case of an error.

Error Callbacks

You can set as many callbacks as needed to run in case of an error:

If there's an error the two defined callbacks will be executed.

Error Logging

To log the possible errors during each run, we can set log_error and error_log_file settings in the configuration file as below:

As a result, if the execution of an event is unsuccessful for some reasons, the error message is appended to the specified error log file. Each entry provides useful information including the time it happened, the event description, the executed command which caused the error, and the error message itself.

It is also possible to send the errors as emails to a group of recipients by setting email_error and mailer settings in the configuration file.

Custom logger

To use your own logger create class implementing \Crunz\Application\Service\LoggerFactoryInterface, for example:

then use this class name in config:

Done.

Pre-Process and Post-Process Hooks

There are times when we want to do some kind of operations before and after an event. This is possible by attaching pre-process and post-process callbacks to the respective event.

To do this, we use before() and after() on both Event and Schedule objects, meaning we can have pre and post hooks on an event-basis as well as schedule basis. The hooks bind to schedule will run before all events, and after all the events are finished.

We might need to use these methods as many times we need by chaining them.

Post-execution callbacks are only called if the execution of the event has been successful.

Other Useful Commands

We've already used a few of crunz commands like schedule:run and publish:config.

To see all the valid options and arguments of crunz, we can run the following command:

Listing Tasks

One of these commands is crunz schedule:list, which lists the defined tasks (in collected *.Tasks.php files) in a tabular format.

Force run

While in development it may be useful to force run all tasks regardless of their actual run time, which can be achieved by adding --force to schedule:run:

To force run a single task, use the schedule:list command above to determine the Task number and run as follows:

Generating Tasks

There is also a useful command named make:task, which generates a task file skeleton with all the defaults, so we won't have to write them from scratch. We can modify the output file later based on our requirements.

For example, to create a task, which runs /var/www/script.php every hour on Mondays, we run the following command:

When we run this command, Crunz will ask about the location we want to save the file. By default, it is our source tasks directory.

As a result, the event is defined in a file named exampleOneTasks.php within the specified tasks directory.

To see if the event has been created successfully, we list the events:

To see all the options of make:task command with all the defaults, we run this:

Debugging tasks

To show basic information about task run:

Above command should output something like this:

Configuration

There are a few configuration options provided by Crunz in YAML format. To modify the configuration settings, it is highly recommended to have your own copy of the configuration file, instead of modifying the original one.

To create a copy of the configuration file, first we need to publish the configuration file:

As a result, a copy of the configuration file will be created within our project's root directory.

The configuration file looks like this:

As you can see there are a few options like source which is used to specify the source tasks directory. The other options are used for error/output logging/emailing purposes.

Each time we run Crunz commands, it will look into the project's root directory to see if there's any user-modified configuration file. If the configuration file doesn't exists, it will use the one shipped with the package.

Development ENV flags

The following environment flags should be used only while in development. Typical end-users do not need to, and should not, change them.

CRUNZ_CONTAINER_DEBUG

Flag used to enable/disable container debug mode, useful only for development. Enabled by default in docker-compose.

CRUNZ_DEPRECATION_HANDLER

Flag used to enable/disable Crunz deprecation handler, useful only for integration tests. Disabled by default for tests.

Contributing

Which branch should I choose?

In most cases you should target branch 1.12.x, as this is active development branch. Branch master is for future release, but all bugs/features should go to 1.11.x anyway.

If You Need Help

Please submit all issues and questions using GitHub issues and I will try to help you.

Credits

• PabloKowalczyk
• Reza Lavarian
• All Contributors

License

Crunz is free software distributed under the terms of the MIT license.