chain-registry icon indicating copy to clipboard operation
chain-registry copied to clipboard

Create a single binary that installs daemons of every chain

Open sunnya97 opened this issue 3 years ago • 8 comments

sunnya97 avatar Dec 18 '21 21:12 sunnya97

this is overkill and more so identifies a lack of tolling to use across chains. I would propose using lens from Strangelove instead. The tool provides a way to work with all chains without needing to download all binaries

tac0turtle avatar Dec 30 '21 12:12 tac0turtle

If anything, it would be nice to have something that generates a script to install a binary, and populate config files / address book based on the chain selected, so node operators can bootstrap more quickly.

nooomski avatar Feb 03 '22 14:02 nooomski

Feels like this goes without saying but any tooling like this should be in a separate repo.

hxrts avatar Feb 04 '22 09:02 hxrts

I think this is effectively what lens is doing

https://github.com/strangelove-ventures/lens

@jackzampolin

sunnya97 avatar Feb 04 '22 20:02 sunnya97

@hxrts how do you feel about docker-compose stuff living here?

We should chainify this, stat.

Needs name better than chain-registry tho.......

faddat avatar Mar 01 '22 11:03 faddat

Agree with @hxrts that this should be in a new repo, similar to lens and Akash's cosmos-omnibus https://github.com/ovrclk/cosmos-omnibus

sunnya97 avatar Mar 01 '22 18:03 sunnya97

I agree with the common sentiment. We are using heighliner for running containerized chain nodes, similar to omnibus. For just about everything else, we use lens.

agouin avatar Mar 01 '22 19:03 agouin

how do you feel about docker-compose stuff living here?

My feeling is this whole repo should be parsable as json-ld. Don't have strong opinions about how deep that data structure should go, but it shouldn't really matter that much. We can always replace inline data with a link or visa-versa.

hxrts avatar Mar 02 '22 13:03 hxrts