search

vulpemventures / nigiri

🍣 A delicious docker box for special Bitcoin, Lightning and Liquid cookings
https://nigiri.vulpem.com
MIT License
273 stars 44 forks source link

Using Nigiri without installing the CLI #177

Closed gunar closed 1 year ago

gunar commented 1 year ago

How do you recommend setting up the development environment for a project that uses nigiri? Would you just add to the README instructions that the developer should install the nigiri CLI locally? Is there a way to avoid having to install it in the development environment? Can I perhaps simply use/reuse this project's docker-compose.yml so that I get everything I need set up with docker compose up? And if that's the case, is there some documentation that might help me in doing so?

I understand that's a lot of questions. My hope is that they'll help me convey a sense of what I'm looking for.

Thanks in advance.

tiero commented 1 year ago

Hey @gunar the CLI indeed abstracts all docker complexities, orchestrate various containers, and expose useful commands for development.

You can def fork the project and copy the docker-compose, but cant really help more than that as the CLI is built with the sole purpose to make it easier :) I would encourage developers to have nigiri installed on their machine.

We also have a GitHub action (which is pulling the CLi and running all the services without the Esplora frontend) ie. nigiri start --ci

gunar commented 1 year ago

Thank you. I'll see how far I can take it just with the docker compose file, and if I see myself missing an easy-to-use CLI I'll come back to nigiri. Thanks again for your prompt response.