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