Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup hubot clone to achieve 100% uptime #3

Open
samuelcouch opened this issue Sep 14, 2015 · 0 comments
Open

Setup hubot clone to achieve 100% uptime #3

samuelcouch opened this issue Sep 14, 2015 · 0 comments

Comments

@samuelcouch
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant