I understand that running applications and services within docker containers generally should leave (almost) no traces and possibly fill up the the disk space. However, for development and debugging purposes, it can be very helpful if some information is retained that permits tracking down bugs or weird behaviours. For many applications and scripts, debug information may be printed to stdout/stderr and end up in the docker logs, but these also get lost when containers is removed.
For your consideration, I'm suggesting to add a way to keep this information if required. Currently I have a patched version of hilbert-station that does that for docker-compose. This approach certainly is not worked out, but may serve as a basis for your consideration.
I have the logs written to the local hilbert-station config directory, which also keeps old configurations. Log rotation might be added to avoid filling up disk space, but that may be a thing of over-engineering it already.
Activating this feature might be done by setting a variable in Hilbert.yml, either for a specific station or for a "station_defaults" template that will get inherited by respective stations. The activation variable could well be the subdirectory within ~/.config/hilbert-station/, e.g. logs, and have it disabled by default (if string empty or not set).
I understand that running applications and services within docker containers generally should leave (almost) no traces and possibly fill up the the disk space. However, for development and debugging purposes, it can be very helpful if some information is retained that permits tracking down bugs or weird behaviours. For many applications and scripts, debug information may be printed to stdout/stderr and end up in the docker logs, but these also get lost when containers is removed.
For your consideration, I'm suggesting to add a way to keep this information if required. Currently I have a patched version of
hilbert-station
that does that fordocker-compose
. This approach certainly is not worked out, but may serve as a basis for your consideration.I have the logs written to the local hilbert-station config directory, which also keeps old configurations. Log rotation might be added to avoid filling up disk space, but that may be a thing of over-engineering it already.
Activating this feature might be done by setting a variable in Hilbert.yml, either for a specific station or for a "station_defaults" template that will get inherited by respective stations. The activation variable could well be the subdirectory within
~/.config/hilbert-station/
, e.g.logs
, and have it disabled by default (if string empty or not set).