From b26da8e3a5f194f18f4efc010ad7c9bd590c23d1 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sun, 3 Jul 2016 17:16:30 -0400 Subject: [PATCH] Be more explicit around the commands being run for the dokku events plugin [ci skip] --- docs/dokku-events-logs.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/dokku-events-logs.md b/docs/dokku-events-logs.md index b6b02dafc..9e2024f4a 100644 --- a/docs/dokku-events-logs.md +++ b/docs/dokku-events-logs.md @@ -15,13 +15,20 @@ events:off # Disable events logger Enable the plugin: +```shell +dokku events:on +``` + ``` -$ dokku events:on Enabling dokku events logger ``` Dokku will then write log entries to ``/var/log/syslog`` as well as a Dokku-specific logs sub-directory ``/var/log/dokku/events.log``, which can be easily displayed with the command `dokku events`: +```shell +dokku events +``` + ``` Jul 3 16:09:48 dokku.me dokku[127630]: INVOKED: pre-release-buildpack( pythonapp ) Jul 3 16:10:02 dokku.me dokku[128095]: INVOKED: docker-args-run( rubyapp ) @@ -42,6 +49,11 @@ Jul 3 16:30:02 dokku.me dokku[131384]: INVOKED: docker-args-run( rubyapp ) ``` You can list all events that are currently being recorded via `dokku events:list`: + +```shell +dokku events:list +``` + ``` =====> Events currently logged docker-args-build