Expand logging instructions to explain underlying docker commands #264
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![hm-linter[bot]](https://avatars.githubusercontent.com/in/5455?s=60&v=4){kind=small}
roborourke
approved these changes
Feb 10, 2021
|
Cheers @kadamwhite |
joehoyle
added a commit
that referenced
this pull request
Jan 22, 2024
5.0.13 - [Backport v5.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #263 6.0.13 - [Backport v6.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #264 8.2.12 - [Backport v8.2-branch] Bump php from 8.2.12-fpm-bookworm to 8.2.13-fpm-bookworm by @hm-backport in #258 - [Backport v8.2-branch] Bump php from 8.2.13-fpm-bookworm to 8.2.14-fpm-bookworm by @hm-backport in #260 - Update Afterburner to 0.5.0 by @joehoyle in #262
joehoyle
added a commit
that referenced
this pull request
Jan 22, 2024
5.0.13 - [Backport v5.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #263 6.0.13 - [Backport v6.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #264 8.2.12 - [Backport v8.2-branch] Bump php from 8.2.12-fpm-bookworm to 8.2.13-fpm-bookworm by @hm-backport in #258 - [Backport v8.2-branch] Bump php from 8.2.13-fpm-bookworm to 8.2.14-fpm-bookworm by @hm-backport in #260 - Update Afterburner to 0.5.0 by @joehoyle in #262
joehoyle
added a commit
that referenced
this pull request
Jan 22, 2024
5.0.13 - [Backport v5.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #263 6.0.13 - [Backport v6.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #264 8.2.12 - [Backport v8.2-branch] Bump php from 8.2.12-fpm-bookworm to 8.2.13-fpm-bookworm by @hm-backport in #258 - [Backport v8.2-branch] Bump php from 8.2.13-fpm-bookworm to 8.2.14-fpm-bookworm by @hm-backport in #260 - Update Afterburner to 0.5.0 by @joehoyle in #262
joehoyle
added a commit
that referenced
this pull request
Jan 22, 2024
5.0.13 - [Backport v5.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #263 6.0.13 - [Backport v6.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #264 8.2.12 - [Backport v8.2-branch] Bump php from 8.2.12-fpm-bookworm to 8.2.13-fpm-bookworm by @hm-backport in #258 - [Backport v8.2-branch] Bump php from 8.2.13-fpm-bookworm to 8.2.14-fpm-bookworm by @hm-backport in #260 - Update Afterburner to 0.5.0 by @joehoyle in #262
hm-backport bot
pushed a commit
that referenced
this pull request
Jan 26, 2024
5.0.13 - [Backport v5.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #263 6.0.13 - [Backport v6.0-branch] Update Afterburner to 0.5.0 by @hm-backport in #264 8.2.12 - [Backport v8.2-branch] Bump php from 8.2.12-fpm-bookworm to 8.2.13-fpm-bookworm by @hm-backport in #258 - [Backport v8.2-branch] Bump php from 8.2.13-fpm-bookworm to 8.2.14-fpm-bookworm by @hm-backport in #260 - Update Afterburner to 0.5.0 by @joehoyle in #262
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on #263 I was a bit stuck before @roborourke explained how to directly access Traefik logs via docker. Once I understood how that logging command works, I found it more useful to directly follow the logs using
dockercommands because it removed some of the boilerplate text from the output and let me see more data at once. I think it would be useful to be explicit about how the logging command works under the hood to de-obfuscate this for developers who may need to dive deeper.