I agree with the approach of Docker but we have to keep in mind that if Docker version gets updated, to ensure that whatever it's deploy did not get affected by the vers update. That's my only concern but I agree that we should simplify what we can and make it easier (ready-to-deploy).
Maybe we talk about different things. What im saying is to make one docker-compose file that will have all scripts. No need to deploy image to docker-hub.
I am in favor in taking whatever approach simplifies usage of the tool for the developer community as it will not only make this easier to consume but easier to support when issues arise.
Can we do this using docker?
like with a simple docker-compose up
totally agree. by making it with docker-compose we will have only one config file and only one line of code to run it
I agree with the approach of Docker but we have to keep in mind that if Docker version gets updated, to ensure that whatever it's deploy did not get affected by the vers update. That's my only concern but I agree that we should simplify what we can and make it easier (ready-to-deploy).
Maybe we talk about different things. What im saying is to make one docker-compose file that will have all scripts. No need to deploy image to docker-hub.
I am in favor in taking whatever approach simplifies usage of the tool for the developer community as it will not only make this easier to consume but easier to support when issues arise.
Support docker now:
github.com/Carry-So/graph-node#1-d...
how can we increase indexing process?