Lifailon/lazyjournal 0.8.0 on GitHub

Full Changelog: 0.7.9...0.8.0

Issues and new features

#23 Added configuration for changing hotkeys and updated installation scripts for loading configuration (fix install.sh: correct binPath and configPath handling by @bitwise-id in #29).
#27 Added ability to change default values via configuration.
Implemented access to logs on a remote machine via ssh without installing lazyjournal on the remote machine. New flag: -s/--ssh, which accepts standard ssh options for configuring the connection (passed as a single argument in quotes).

Example:

lazyjournal --ssh "lifailon@192.168.3.101 -p 22"
# If sudo is supported without entering a password
lazyjournal --ssh "lifailon@192.168.3.101 -p 22 sudo"

Note

Access to remote machines is possible only with an ssh key (password access is not supported).

Fixes and performance

Added getting a list of all Kubernetes pods (without being tied to a specific namespace in the current configuration) and access to pod logs from any namespace (if there is appropriate access).
Added color highlighting of pod and k3s from Rancher container logs in the file system (the main list - System var logs), which are accessible on any node (including Worker) with root rights.
Added support for a shortened format for filtering by time (for example, from -48h to -24h or +1h to +30m, etc.).
Added a preliminary check for the presence of text in the filter field to clear the text by default on the first press of the keyboard shortcut before exiting and additional buttons (by default) [/] to switch lists.
Added error notification when enabling the tailspin painting mode if it is not installed or there is no access to docker logs in json format (from the file system).
Added an empty line at the end of any log output, and removed an extra empty line when reading docker logs in json mode.
Improved sorting of log lists in the file system by date (added modification time, as well as filtering accuracy to the minute).
Changed loading of any log to background loading in a goroutine for smooth operation of the interface (fast mode is a beta feature).

Important

Fast mode can cause increased load on the processor or work unstably, so it can be disabled in the configuration using the settings.disableFastMode parameter. If you notice any errors in the work, please report them using the Issue section (we will first disable this mode for comparison).