4 ms·
You can trivially make one with a secondary Heroku app that runs a single non-web dyno running the clock process of your choice, making http calls to your prima
by zrail 14y ago
You can trivially make one with a secondary Heroku app that runs a single non-web dyno running the clock process of your choice, making http calls to your primary app.
edit: Please note that this could be against the Heroku terms of service.
- carsongross 14y agoWell, I'd pay, say, $10 a month for a service that was simple, offered some retry algorithms, logged responses, gave me a nice UI for the whole thing and worked reliably (unlike dynos on Heroku, which are nuked regularly.) Not rocket science, to be sure, but I'd rather not build and maintain the infrastructure. Or I'd rather build and maintain only that infrastructure.
- zrail 14y agoNow you've got me thinking. If you're serious send me an email (in my profile) and let's talk.
- themckman 14y agoThis is essentially how App Engine does scheduled jobs. You define the schedule and give it an endpoint in your app to hit. The tricky part with this is that all the limits that come with web requests are imposed on your jobs which may be a problem.