GFY
Sorry, I mean GM. I think.
#LND (#bitcoin #lightning) on Linux is now "Easy AF" with #Parmanode
Wake up.
Fucken, wake up.
You know that face ppl make when ur explaining they've been lied 2 their whole life, everything is a scam, and they're working 2 earn money their rulers create for free, while they're trying 2 be polite and not verbalise, "you're crazy", but have no counter?
Got that face today.
It's here!
#Parmanode has BTCPay on #Linux Desktop. Install and run with just a few clicks from the menu options
Plus - #Bitcoin Core, Fulcrum #Electrum server, Tor, Docker, and Parman's cheek
Mac users - BTCPay coming soon for you too, dontchu worry
I don't know about normal people, but I certainly can hear the faint but slowly swelling sounds of bull hoofs stirring in the dusky distance.
Or are they #Bitcoin miners?
Want to hear about the pain I went through today and how I lost another 4 hours because of #Parmanode (easy AF #Bitcoin node for desktop computers), and my desire to get #BTCPay running easily with a few clicks?
It's related to a BTCPay docker build from scratch, because why not?
For the life of me, I couldn't figure out why I couldn't get BTCpay to connect to the block explorer in the background...
I isolated it to the script not fulfilling the command:
docker exec -it btcpay bash -c "/home/foo/run.sh"
evvvVVVENTUALLY...
when I looked inside this damn http://run.sh script (http://run.sh is by btcpay server, I didn't write it), I saw it was running a NBXplorer file, but it was a relative path.
FFS, when executing this script using the absolute path /home/foo/run.sh , it was not locating the target in the script. FLM, hours lost...
But the plot thickens...
Thinking I found the problem and overcome it by:
cd /home/foo && ./run.sh
I though for sure this would work.
FAIL. NBXplorer not running...
I can manually copy and paste the contents of the docker exec command in the container and get it running, but not when executing it from the script.
The other docker exec command, http://run.sh, for btcpay was working fine. Why the issue? Can you guess?...
The second exec command, for nbxplorer, needed to be delayed by a few seconds with a sleep 4 command. Then it works. Fuck. It was almost by chance as this "trick" worked with something else previously.
I suppose the code proceeds before docker is ready to run the next command in the container, IDK, but narrowing the problem down took ages.
Onwards!
The good news is that BTCPay for #Pamanode is only days away.
You haven't lived unless you've experienced the deep satisfaction of making your own Dockerfile from scratch.
I stackethid
Similar saying in the sex industry
Great day Bitcoining and computerising today. 6.20 am, better sleep a little
Dayem, chunky chicken liver pate goes amazingly with whiskey at 1 am
You should know the 6 reasons to run a knowde
https://armantheparman.com/why-should-you-run-your-own-bitcoin-node/