Ehh, the docker compose solution wasn't that bad vs. mynode IMO. There wasn't much I couldn't do with it, escept a few really small docker-compose tweaks 🤷♂️
That said, if those aren't advanced enough...nix-bitcoin blows them all out of the water 😎
Ehh, the docker compose solution wasn't that bad vs. mynode IMO. There wasn't much I couldn't do with it, escept a few really small docker-compose tweaks 🤷♂️
That said, if those aren't advanced enough...nix-bitcoin blows them all out of the water 😎
*without a few, not except a few
Shill me your nix-bitcoin 0-100 installer and I'll be on it in no time. @n1ckler got me interested a while ago, but getting off zero seemed hard at the time and I never got around to it.
Problem with the dockers is I can't do stuff like
[[ grep '$pattern' bitcoind.log ]] && bitcoin-cli … blabla | lncli … thisandthat …
I.e. scripting across services. Which used to be the whole point of Unix, of which Linux is a rather tumor-esque variant.
You can run any command in any container from the host; you can definitely pipe bitcoin-cli output to lncli. If you need to actually change the images (nit just the compose files), then it's a bit much.
For cross service scripting, nix is top tier IMO, but you're right, without any experience with the nix language, it's a little bit of a learning curve.
Just saying stuff like this sucks: Extra output to stdout makes scripting cumbersome to impossible, super long command as replacement suggestion, and that command doesn't even work. And if it did, it probably wouldn't do transparent I/O redirection.
umbrel@umbrel:~ $ bitcoin-cli --version 2 >/dev/null
*** Deprecation notice ***
In a future version of Umbrel, 'bitcoin-cli' will be removed.
Please instead use:
./scripts/app compose bitcoin exec bitcoind bitcoin-cli
[output of --version deleted for clarity]
umbrel@umbrel:~ $ ./scripts/app compose bitcoin exec bitcoind bitcoin-cli --version
-bash: ./scripts/app: No such file or directory