Make config clearer in log-strategies.md (#73) (#77)

This wasn't working for me because nothing in here says it all needs to be the value a `:log-to` key in the container config map. Reading the code and adding that made it work. Figured it might be nice to clarify that for others too.

Co-authored-by: Wes Morgan <github@wesmorgan.me>
This commit is contained in:
Tim Zöller 2024-04-13 09:08:45 +02:00 committed by GitHub
parent 49f547585e
commit 233c3883eb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -4,13 +4,13 @@ This library offers two ways to access the logs of the running container: The :s
## String Strategy ## String Strategy
The `:string` strategy sets up a function in the returned map, under the `string-log` key. This function enables the The `:string` strategy sets up a function in the returned map, under the `:log` key. This function enables the
dumping of the logs when passed to the `dump-logs` function. dumping of the logs when passed to the `dump-logs` function.
Example: Example:
```clojure ```clojure
{:log-strategy :string} {:log-to {:log-strategy :string}}
``` ```
Then, later in your program, you can access the logs thus: Then, later in your program, you can access the logs thus:
@ -29,6 +29,6 @@ This way you can pass the container logging on to the logging library of your ch
Example: Example:
```clojure ```clojure
{:log-strategy :fn {:log-to {:log-strategy :fn
:function (fn [log-line] (println "From Container: " log-line))} :function (fn [log-line] (println "From Container: " log-line))}}
``` ```