Still im confused. cncli is not a stand alone program? does it work in conjunction with cntools? what is coincashew guide in reference to here?
 ok as far as i can see cntools is used to basically setup a node from scratch. However. Im not setting up a node from scratch, the node is running. i want to use cncli to interact with the node socket, but cant figure out “how” the whole idea behind cncli and cntools works together, it seems im missing a bunch of scripts having only compiled and installed cncli.
If you really want to know what you are doing, you will look at both and do it your own way without all the copy and pasting and a deep look at the scripts, what they are doing and why and if you really need them.
Ok, usually i just manage my node manually. which is as expected a very manual process having built my own scripts etc.
what o was really interested in is using cncli as an interface to the node socket. Where i got tripped up is learning that cncli and cntools are usually used together and have a few dependencies together.
So, if i go and use cntools from scratch and use the pre-reqs i get cntools file structure. which i dont really want/need as i have the node running.
Ill take a look at cntools and see what i can get from it in terms of scripts to get cncli running
Thanks @HeptaSean , yeah i dont need cntoolsetc to manage my nodes, i was just interested in how cntools and cncli work. more specifically cncli as a standalone. You’re correct, there is no mention of cntools on cncli github, which is why i got confused why the sync script was in cntools repo.
i have since managed to sync using ./cncli sync and modifying the env files to suit my setup.