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
The best way I can think to do this right now - and it's not good - is to have an app-follow-logs hook that only has one listener on it (part of the same plugin that cats logs for the running container), which gets fired after(?) the app-logs hook. This hook script then doesn't exit until it receives the applicable signal.
Anyway, this is a future feature.
The text was updated successfully, but these errors were encountered:
Per heroku:
The best way I can think to do this right now - and it's not good - is to have an
app-follow-logs
hook that only has one listener on it (part of the same plugin that cats logs for the running container), which gets fired after(?) theapp-logs
hook. This hook script then doesn't exit until it receives the applicable signal.Anyway, this is a future feature.
The text was updated successfully, but these errors were encountered: