ResqueScheduler into Fresque about fresque

[wa0x6e]

You can't (yet). The methods are from the dependencies, but not implemented yet. It's in my todo list

[mrjgreen]

Okay thanks.

[pwhelan]

I had a working patch (which I nuked) that allowed invoking ResqueScheduler by setting the binary for the queue. The resulting queue definition I had was this:

[Qeueus]

... 

_schdlr_[workers] = 1
_schdlr_[interval] = 15
_schdlr_[bin] = ./resque-scheduler

I'll reimplement the patch now and do a pull request. If someone has a more elegant solution that would be nice but this should work for now.

[wa0x6e]

It's not what I had in mind. My goal is to have something similar to https://github.com/kamisama/Cake-Resque/blob/master/Console/Command/CakeResqueShell.php#L420

[pwhelan]

Would the idea then to have a special INI settings specifically for invoking Resque-Scheduler then? Should I work on that and add it to the Fresque section? Like so would be my idea then:

[Fresque]
...
; Invoke the scheduler
scheduler = true

The resque-scheduler binary could be searched out relative to the autoload path upon loading. I can give it a try tomorrow.

[wa0x6e]

My goal is to have the same thing on Fresque and CakeResque, same settings, etc ... to preserve compatibility between these 2 scripts. Fresque is just a generic version of CakeResque.

[pwhelan]

I had not even looked at your implementation for CakeResque. Would it work then to include a new section specifically for the Scheduler?

The format (from what I gather) would be:

[Scheduler]
enabled = true ; false (default)
log = /tmp/resque-scheduler.log ; default to using the fresque log?
user = apache
env[some] = envvariable
env[and] = someothervariable
lib = ./vendor/kamisama/php-resque-ex
interval = 5 ; should I bother make this a part of a subsection of sorts?
loghandler = Cube
loghandlertarget = udp://127.0.0.1:1180

The actual LOGHANDLER and LOGHANDLERTARGET should be the same as the other workers, should it not? The case could be made to expose them as sub settings in the same way as env?

Another alternative to make it almost entirely compatible, but also extremely loooong winded.

[Scheduler]
enabled = true ; false (default)
log = /tmp/resque-scheduler.log ; default to using the fresque log?
Env[some] = envvariable
Env[and] = someothervariable
; add the other bit of the path and expose as RESQUE_PHP to the binary
lib = ./vendor/kamisama/php-resque-ex
; I could see these settings just being a direct key off of [Scheduler]
Worker[interval] = 5
Worker[user] = apache
; This would probably need to be it's own section, unless we could live
; with LOGHANDLERTARGET and LOGHANDLER, which would make more sense
; for fresque.ini
Log[target] = udp://127.0.0.1:1180
Log[handler] = Cube

Any further thoughts?

[pwhelan]

I'll do a pull request for variant #1 and we can see where we go from there.

[wa0x6e]

If you don't mind, I'm working on it now. I prefer to have something very close to the original CakeResque implementation to keep the compatibility.

[wa0x6e]

Check the latest master.

Update composer dependencies with composer update, then enable the scheduler in the .ini file in the [Scheduler] section.

You can then start the scheduler worker with fresque startScheduler.