-
Notifications
You must be signed in to change notification settings - Fork 642
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Every Minute event #1260
Comments
Issue can be closed. |
I don't think it should be closed. Ideally, I think it should be even more like Laravel Scheduler. More flexibility, repeating jobs, etc. |
I kind of agree, though Scheduler can be used for repeating jobs, you can
just re-create it after its run. I'll probably document some examples at
some point.
On Thu, 23 Mar 2017 at 12:23, Fred Calsen ***@***.***> wrote:
I don't think it should be closed. Ideally, I think it should be even more
like Laravel Scheduler.
More flexibility, repeating jobs, etc.
Josh's Scheduler is more for one-off jobs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1260 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAYq-4A9wkOGaqMxoZhNtfOZ_wsivAhZks5romQ3gaJpZM4LyNzD>
.
--
-Josh
angell.io - specialist Craft CMS development and consultancy
|
Going to leave it open, because we definitely have plans of doing something like this in core. |
Great job on the plugin, @joshangell! |
I like how Laravel Scheduler allow you to both run console commands, closures and Would be a ideal inspiration source for how this could work in the core. |
I found https://github.com/omnilight/yii2-scheduling today. Looks like a good base to use for adding this. |
We’re using that omnilight/yii2-scheduling package in Craftnet. Works well! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
It would be great it there was an event that Craft triggers every minute. The dev sets up a cron that calls a controller action to make this possible, and would then be able to do all kind of cool things when listening to that event.
craft()->on('global.everyMinute', function(Event $event) {
$interval = $event->params['interval'];
});
The text was updated successfully, but these errors were encountered: