pull down to refresh
after `wget -qO- https://tdeploy.lightning.pub | bash'
Script version 0.2.2
2025-11-03 23:02:19 Detected OS: Linux
2025-11-03 23:02:19 Detected ARCH: amd64
2025-11-03 23:02:19 Installing LND...
2025-11-03 23:02:20 LND is already up-to-date. No action needed.
2025-11-03 23:02:21 Checking for Node.js...
2025-11-03 23:02:25 Node.js is not installed. Installing the LTS version...
2025-11-03 23:02:25 Failed to install Node.js.
2025-11-03 23:02:25 ERROR: Failed to install Node.js
2025-11-03 23:02:25 Exiting with status 1
2025-11-03 23:02:25 Cleaning up temporary files...
After I ran
cat /tmp/lightning_pub_install.logI got this:
$ cat /tmp/lightning_pub_install.log cat: /tmp/lightning_pub_install.log: No such file or directoryreply
afterwget -qO- https://tdeploy.lightning.pub | bash
even from a trusted domain, piping from wget or curl into bash directly is a bad habit. I strongly recommend saving the script locally, which gives you the chance to review its steps at your leisure before running them, rather than reconstructing the steps it has already taken in retrospect.
reply
my bad, it pulled from the wrong branch
try that one more time, the script should now say 0.2.3 at the top confirming it's the latest...
reply
It does say 0.2.3, but same result:
Script version 0.2.3 2025-11-03 23:18:04 Detected OS: Linux 2025-11-03 23:18:04 Detected ARCH: amd64 2025-11-03 23:18:04 Installing LND... 2025-11-03 23:18:05 LND is already up-to-date. No action needed. 2025-11-03 23:18:05 Checking for Node.js... 2025-11-03 23:18:11 Node.js is not installed. Installing the LTS version... 2025-11-03 23:18:11 Failed to install Node.js 2025-11-03 23:18:11 ERROR: Failed to install Node.js 2025-11-03 23:18:11 Exiting with status 1 2025-11-03 23:18:11 Cleaning up temporary files... siggy@siggy-XPS-13-9360:~$ cat /tmp/lightning_pub_install.log cat: /tmp/lightning_pub_install.log: No such file or directory
reply
grrr... tricky log...
just made another push to re-order things, try again if you would... (will still say 2.3)
reply
wget -qO- https://tdeploy.lightning.pub | bash
Please don't encourage anyone to develop the habit of piping directly from curl/wget into bash!
Downloading a temporary copy gives the opportunity to look over and possibly customize for your system before running it, and also makes it easier to resume from partway if it failed and needed intervention.
reply
Then we are going bsck to square one where the new user is lost in complex commands.
A single line comnand is much easier for any user.
If you really want to help, take the software and make it a flatpak. We have to make it easier not more complicated.
reply
It's probably worth to define which kind of user are we talking about, because not everyone operate cli and not everyone is comfortable running flatpaks without knowing what's inside.
These are two different scenarios, and LNpub is probably at an early stage still. Feedback like this help the product grow, offering various options for different type of users could be really helpful.
reply
not everyone operate cli and not everyone is comfortable running flatpaks without knowing what's inside.
Last time I setup a desktop environment, KDE Plasma included a graphical installer that handled all the Flatpak machinery while still showing you who the publisher was. I'm not familiar enough with the entire "Desktop Linux" space to make an absolute comparison, although the UX seemed like something a non-technical user could figure out and even rely upon for making security-related decisions.
reply
I realise there's a tradeoff, and you're definitely correct about the usability.
Maybe the better approach is a verbal warning, separate from the copy-pasteable command, along the lines of "this command installs a program, don't run it on critical systems" and encouraging that people have separate hardware for critical systems. That's definitely twice as much maintenance, although it is much easier for someone to reason about security considerations when the sensitive system is a physically separate computer.
reply
It's a pretty common practice, I think I borrowed the idea from nvm, bun, and other things
Even more stuff just adds apt repos to the keyring which is worse imo.
This way you can view the code in browser and see it runs from GitHub.
We did recently drop the sudo requirement for user space isolation.
It's really meant for quick lean VPSs or old laptops nodes without the docker bloat.
If someone has a critical system and isnt cloning from GitHub manually they got bigger issues.
reply
reply
Thanks, looks like the node installer isn't providing detail
Try this if you would, it's not the pub installation itself but just the nodejs piece, it should be more verbose... and if it just works for some reason the next run of the script will install pub since the dependency will have been met
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash && export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && nvm install --ltsreply
reply
I've never seen that before on an Ubuntu system, its a system level dependency that nvm is trying to use that must not typically use Snap
Try switching out the snap version of curl for the regular version and see if that helps a re-run of the nvm installer
sudo snap remove curl && sudo apt install curlreply
Looks like it:
export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm [ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion Installing latest LTS version. Downloading and installing node v24.11.0... Downloading https://nodejs.org/dist/v24.11.0/node-v24.11.0-linux-x64.tar.xz... ########################################################################################################################################## 100.0% Computing checksum with sha256sum Checksums matched! Now using node v24.11.0 (npm v11.6.1) Creating default alias: default -> lts/* (-> v24.11.0)
reply
excellent!
The pub install script should work now as it will detect nodejs as already installed and skip that step
Was just googling and it seems the curl issue presents itself under some condition where it was installed via snap, other nvm users ran into it but they closed the issue without a workaround: https://github.com/nvm-sh/nvm/issues/3000
reply
reply
thanks for bearing through it, keep me posted, of all the things I thought I might debug this week curl wasn't one of them... wow
wget -qO- https://tdeploy.lightning.pub | bashcat /tmp/lightning_pub_install.log