Download the PHP package ezsystems/ezstudio-cron without Composer
On this page you can find all versions of the php package ezsystems/ezstudio-cron. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ezstudio-cron
ezstudio-cron
This package exposes cron/cron package for use in eZ Platform (or just plain Symfony) via a simle command
ezpublish:cron:run.
This is not a replacement for cron/cron-bundle but rather a simpler alternative to it which can more esaily grow into focusing more on eZ Platform needs in the future including e.g. support for handling cron jobs across a cluster install _(separating jobs that should run on all nodes vs jobs that should only be run on one at a time and a lock system to go with it for instance).
Setup system cron
Pick your systems cron / scheduling and setup ezpublish:cron:run command to run every minute and optionally specifying category (default: default):
Example for Linux crontab (crontab -e):
Setting up own cron commands
Setting up own cron jobs is as simple as tagging services for your existing Symfony Commands.
The tag takes the following arguments:
name:ezpublish.cron.jobschedule: Takes any kind of format supported by cron/cron, which mimics linux crontab format. E.g.* * * * *category: (Optional, by default:default) Lets you separate cronjobs that should be run under different logic then default, e.g. infrequent jobs (NOTE: Means end user will need to setup several entries in his crontab to run all categories!)
