You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Heroku requires 6 hours of downtime for free plans, Owlbot sleeps from 11:59PM - 6AM (the 11:59pm isn't a hard number, but that's when keep-alive pings stop firing off, Heroku will idle and kill the process +/- 10 minutes after that. 6AM is when the wake up is absolutely fired off).
The idea would be to create a complete clone of owlbot that will live in a separate app entirely, but utilize the same redis datastore for complete persistence.
Possible solution
The main challenge here is making sure that both bots aren't awake at the same time as this will result in double messages being posted.
One way to achieve this would be to write a bash script that would kill Owlbot at a specific time, and startup the clone.
The text was updated successfully, but these errors were encountered:
Background
Since Heroku requires 6 hours of downtime for free plans, Owlbot sleeps from 11:59PM - 6AM (the 11:59pm isn't a hard number, but that's when keep-alive pings stop firing off, Heroku will idle and kill the process +/- 10 minutes after that. 6AM is when the wake up is absolutely fired off).
The idea would be to create a complete clone of owlbot that will live in a separate app entirely, but utilize the same redis datastore for complete persistence.
Possible solution
The main challenge here is making sure that both bots aren't awake at the same time as this will result in double messages being posted.
One way to achieve this would be to write a bash script that would kill
Owlbot
at a specific time, and startup the clone.The text was updated successfully, but these errors were encountered: