Bricklogger 0.2.3

Bricklogger 0.2.3

Installing

• Bricklogger is installed per login with uv: uv tool install bricklogger,
  then bricklogger init. uv brings a Python that fits, and everything stays
  in that login's home directory. The install script is gone, and so is
  installing as root.
• bricklogger services install [--web] [--mcp] runs the daemon, and the
  web interface and the MCP server when asked, as systemd --user services
  that start at boot; init offers it as its last step.
  services uninstall and services status complete the group.
• Plugins are kept in uv's record of the tool environment, so
  bricklogger update and uv tool upgrade bricklogger keep them. Do not run
  uv tool install bricklogger again over an installation with plugins: it
  uninstalls every plugin not named with --with.

Moving from an installation made with the install script

• Remove it with the script it came from, keeping the configuration and the
  data:
  curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/download/v0.2.2/install.sh | sudo sh -s -- --uninstall
  (without sudo for an installation in a home directory). Then
  uv tool install bricklogger, add the plugins again with
  bricklogger plugins add, copy the configuration and the data from
  /etc/bricklogger and /var/lib/bricklogger to ~/.config/bricklogger and
  ~/.local/share/bricklogger if they lay there — with the env file, and
  with data_dir in daemon.yaml changed to the new place — and run
  bricklogger services install.

Changed

• /etc/bricklogger is no longer looked for; the configuration is in
  ~/.config/bricklogger unless --config-dir or BRICKLOGGER_CONFIG_DIR says
  otherwise. The container is unchanged.
• The unit templates are user units: no User= line and no network target.
  bricklogger update rewrites only the units that are set up.