Some of the scripts running in GooeyJr such as greeting.coffee and tell.coffee require a redis database where they can store data. While the default location is for hubot-redis-brain (which persists the data stored in Hubot) is localhost on Heroku, hosting it there would mean that the data will not persist between deploys and when the Heroku app restarts.
Currently, to tackle this, GooeyJr makes use of Heroku Redis which provides 25MB of redis storage for free but it's not for certain how long this will last. It would be good if we could come up with a long-term solution for storing this redis data.
One possible solution would be to host our own redis server (making sure to import the data already hosted on Heroku Redis).
Some of the scripts running in GooeyJr such as greeting.coffee and tell.coffee require a redis database where they can store data. While the default location is for hubot-redis-brain (which persists the data stored in Hubot) is localhost on Heroku, hosting it there would mean that the data will not persist between deploys and when the Heroku app restarts.
Currently, to tackle this, GooeyJr makes use of Heroku Redis which provides 25MB of redis storage for free but it's not for certain how long this will last. It would be good if we could come up with a long-term solution for storing this redis data.
One possible solution would be to host our own redis server (making sure to import the data already hosted on Heroku Redis).