One of my first thoughts looking at the docs is recurring tasks on a schedule.
Could a cron job or something similar wake up the server?
The hibernating sprite is completely “off”, moved onto other storage and no CPU, so I don’t think it’s possible for it to wake itself up.
You could have one sprite that is always on that sends cron wakeup calls to any number of sleeping sprites that have a service listening for requests (a network request will wake up a sleeping sprite). There are “Hosted Cron” or “HTTP Scheduler” services that you could use to trigger a wakeup if you don’t want to roll your own scheduler.
Just make sure you’re covering your bases in terms of authenticating what is sending the ping or you’ll might get a lot of random traffic on that port.
1 Like
I’m totally thinking ahead - but e.g. I have workflows on pipedream that I run on an interval that I’d run in a sprite if I was doing it now.
Having a built-in auto-wakeup sounds like it would accommodate many workflows.
Hooking the native cron system into an external orchestration to re-awaken and run that cron sounds like it fits the idea of a VM.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.