Comments (10)
You can't (yet). The methods are from the dependencies, but not implemented yet. It's in my todo list
from fresque.
Okay thanks.
from fresque.
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.
from fresque.
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
from fresque.
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.
from fresque.
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.
from fresque.
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?
from fresque.
I'll do a pull request for variant #1 and we can see where we go from there.
from fresque.
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.
from fresque.
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
.
from fresque.
Related Issues (20)
- fresque stop doesn't clear workers after stopping them HOT 2
- Tag new version with Scheduler support HOT 2
- resume command doesn't work HOT 5
- Specifying worker names with stop command HOT 4
- Starting worker ..................... Fail HOT 1
- Failed to start worker when server is booting HOT 3
- Composer Requirements HOT 1
- Workers disappearing HOT 4
- need for authentication support HOT 1
- question re fresque.ini HOT 3
- PHP Warning at the end of 'fresque test'
- Link in project description gives 404 HOT 1
- Travis build status and link appears to not be working.
- can pass -c to enquue command
- Unable to create more than one worker HOT 1
- What's the point of running same scheduler workers count as in default queue? HOT 2
- fresque is stopping everyday HOT 1
- Memory Problem free(); HOT 1
- Version bump? 1.3.2 or 1.4.0?
- Scalability: Scaling fresque
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fresque.