diff --git a/backup/README.md b/backup/README.md index a713fd312..0ced6d5f7 100644 --- a/backup/README.md +++ b/backup/README.md @@ -18,6 +18,28 @@ plugin and `backup-cli` like a binary. After `uv` is installed and you followed lightning-cli plugin start /path/to/backup.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/cl-zmq/README.md b/cl-zmq/README.md index c67475f68..b6f008797 100644 --- a/cl-zmq/README.md +++ b/cl-zmq/README.md @@ -14,6 +14,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/cl-zmq.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/clearnet/README.md b/clearnet/README.md index 9bc924bc4..6c9a1fb8a 100644 --- a/clearnet/README.md +++ b/clearnet/README.md @@ -12,6 +12,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/clearnet.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/currencyrate/README.md b/currencyrate/README.md index 0c60cee6c..361bfb385 100644 --- a/currencyrate/README.md +++ b/currencyrate/README.md @@ -12,6 +12,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/currencyrate.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/donations/README.md b/donations/README.md index 32f573f3e..a6de941b0 100644 --- a/donations/README.md +++ b/donations/README.md @@ -7,6 +7,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/donations.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/feeadjuster/README.md b/feeadjuster/README.md index 8ef669a97..486cc5692 100644 --- a/feeadjuster/README.md +++ b/feeadjuster/README.md @@ -14,6 +14,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/feeadjuster.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/historian/README.md b/historian/README.md index 2fccd100a..7640b15d5 100644 --- a/historian/README.md +++ b/historian/README.md @@ -21,6 +21,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/historian.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/monitor/README.md b/monitor/README.md index f08dfd549..f8882cb9b 100644 --- a/monitor/README.md +++ b/monitor/README.md @@ -11,6 +11,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/monitor.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/persistent-channels/README.md b/persistent-channels/README.md index a33099736..cee765110 100644 --- a/persistent-channels/README.md +++ b/persistent-channels/README.md @@ -7,6 +7,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/persistent-channels.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/prometheus/README.md b/prometheus/README.md index 60485f8e4..89354f72e 100644 --- a/prometheus/README.md +++ b/prometheus/README.md @@ -25,5 +25,27 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/prometheus.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/rebalance/README.md b/rebalance/README.md index e258e7632..bb881bbc7 100644 --- a/rebalance/README.md +++ b/rebalance/README.md @@ -12,6 +12,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/rebalance.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation) diff --git a/sauron/README.md b/sauron/README.md index 97760b9d6..f945c6b2c 100644 --- a/sauron/README.md +++ b/sauron/README.md @@ -41,3 +41,26 @@ Hidden services are also supported : ``` lightningd --testnet --disable-plugin bcli --plugin $PWD/sauron.py --sauron-tor-proxy localhost:9050 --sauron-api-endpoint http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/testnet/api/ ``` + + +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. diff --git a/summary/README.md b/summary/README.md index f122ce7c5..9c5e2ca08 100644 --- a/summary/README.md +++ b/summary/README.md @@ -13,6 +13,28 @@ plugin like a binary. After `uv` is installed you can simply run lightning-cli plugin start /path/to/summary.py ``` +If you use `systemd` to start CLN, you must have `uv` in the `PATH` that `systemd` uses, which is likely different than the `PATH` from your shell. Most `uv` installation methods install `uv` into your user's home directory (`~/.local/bin` or `~/.cargo/bin`), which `systemd` cannot access. + +You can either: + +**Option 1: Install `uv` system-wide** (recommended): +```bash +curl -LsSf https://astral.sh/uv/install.sh | sudo env UV_INSTALL_DIR="/usr/local/bin" sh +``` + +**Option 2: Copy your existing user installation**: +```bash +sudo cp "$(command -v uv)" /usr/local/bin/uv +``` + +**Option 3: Configure your systemd service** to use a custom `PATH` (see systemd documentation). + +To verify `uv` is accessible to systemd: +```bash +sudo systemd-run --user --wait command -v uv +``` +This should output `/usr/local/bin/uv`. + For general plugin installation instructions see the repos main [README.md](https://github.com/lightningd/plugins/blob/master/README.md#Installation)