As systemd service vs. modern python venv deployment?

[Matthias84]

Hi ther,e, I'm pretty happy by invoking mqttwarn manually 😄

But I tried to transform it to a working systemd service, based upon mqttwarn.service unit example. Unfortunatly modern Debian based OS omit the unmanaged use of pip and encourage you to make use of a virtualenv isolation. Unfortunatly this isn't covered by the .service example file and I strugle to invoke the python interpreter from this venv with the correct mqttwarn source?

P.S. Where are this example files are stored if you just pip install mqttwarn in a venv?

[amotl]

Hi @Matthias84. Thanks a stack for writing in. The designated way to install Python programs on Linux after distributions rightfully started to reject letting pip install things into system directories, is to use pipx instead.

On Debian, it can be installed using apt install pipx, at least on more recent versions of Debian, see ¹.

docker run --rm -it debian:bookworm bash
export PATH=$PATH:/root/.local/bin  # Needs to go into ~/.bashrc.
apt install pipx
pipx install mqttwarn

mqttwarn --version
mqttwarn 0.35.0

Footnotes

1. https://packages.debian.org/search?keywords=pipx ↩