Integration with Google App Engine scheduler
skor - April 5, 2009 - 13:58
| Project: | Poormanscron |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | skor |
| Status: | won't fix |
Description
I wrote a module that works with a cron schedule service that runs on Google Apps Engine. You have to set up a scheduled request of your cron.php on his GAE service and his service expects an auth code in response. So I just implemented hook_cron and printed out the auth code.
Right now, it's a separate module, but I could re-work it as another option within Poormanscron if there's any interest.
Here's a link to the GAE Scheduler service if anyone wants to check it out.
#1
Grr. botched the link. It's http://schedulerservice.appspot.com/
#2
#3
Here it is as a separate module called gaecron. In this form, if a user were to enable it in addition to the existing poormanscron, the gaecron would get triggered by a page load, and print out the auth code in the middle of a normal html page. So, we could put lots of warnings about not enabling them both together, or we could mod the existing poormanscron and put an exception so it wouldn't invoke gaecron.
@Uwe, I'd like to hear your thoughts about packaging this with your module. Good idea? Not worth your time? I only wrote this because:
#4
Minor mods after running the coder module...
#5
Just curious who's maintianing this module. I see releases from Uwe, Rob Loach, and ax, but kiam and gpk
Happy for feedback from any of you.
#6
Fixed .info file so shows up as part of poomanscron.
#7
The list of the maintainers is linked to the project page.
#8
Thanks. I hadn't noticed that before.
#9
Very interesting. So the scheduler calls cron.php, receives the authentication code, and then this allows it to call it next time? What if we just added a "Output after cron run" option in Poormanscron?
#10
I think you'd want some additional logic to prevent the output if the cron.php if it was triggered by a user page load. I'd be afraid of writing the code out in the middle of a user's page view.
#11
I guess I didn't really answer you first question. Yes. the scheduler will request the page the first time but if it gets a successful page load without its confirmation code, it will disable future page request until you go back and re-enable it.
I guess this is sort of an alternative to the current method, though it does introduce an external dependency. I just didn't want to throw out a separate module and cause confusion.
#12
Just checking on if this should be a)merged in poormanscron, b) separate module, c) dropped from lack of interest.
No rush, I'm actually a bit busy now, but I stumble on it again once in a while.
#13
This isn't appropriate for poormanscron. You should just implement this as your own small custom module, seeing as no one else has requested this type of feature and it is a very specific feature request.
#14
Possibly couldn't you also use something like http://drupal.org/project/site_verify ?