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
Hi, I figured there was no timeout to the redis connexion, and both need to up when tipboard starts, otherwise it'll the crash. Since I am trying to dockerize everything and put that in some swarm, I now have redis and tipboard that start separately in 2 different containers, that start in an unpredictable order, meaning that tipboard won't work if it boots before redis. Would it be possible to configure a timeout for the redis connexion ? That way tipboard could way for a specific amout of time before giving up on booting.
Nice tool btw, props to the team.
The text was updated successfully, but these errors were encountered:
Django can start without redis to be up, only when a client connection is started that become to be a requirements, even if redis is slow to start, django will start automaticaly the connection again after a failed.
Hi, I figured there was no timeout to the redis connexion, and both need to up when tipboard starts, otherwise it'll the crash. Since I am trying to dockerize everything and put that in some swarm, I now have redis and tipboard that start separately in 2 different containers, that start in an unpredictable order, meaning that tipboard won't work if it boots before redis. Would it be possible to configure a timeout for the redis connexion ? That way tipboard could way for a specific amout of time before giving up on booting.
Nice tool btw, props to the team.
The text was updated successfully, but these errors were encountered: