LBRYCommunity/lbry-docker
1
0
Fork 0
Code Issues 2 Pull requests 2 Projects Releases 1 Packages Wiki Activity
lbry-docker/chainquery
History
Leopere 8d7c2847cf
We could use more powers (all the sudo's)
2018-11-08 17:06:35 -05:00
..
.dockerignore Chainquery works mostly and so does lbrycrd 2018-11-04 22:44:00 -05:00
.env Chainquery works mostly and so does lbrycrd 2018-11-04 22:44:00 -05:00
.gitignore Chainquery works mostly and so does lbrycrd 2018-11-04 22:44:00 -05:00
chainqueryconfig.toml chainquery needs to be .3 2018-10-10 20:59:58 -04:00
db-seed.sha Adding base database seed script 2018-10-11 22:04:22 -04:00
debugpaste-it.sh MAINTAINER is deprecated in Dockerfile. COPY is preferred over ADD in Dockerfile if additional functonality of ADD is not being used. Improved Shebang lines in many files. 2018-10-14 18:00:06 +05:30
docker-compose.yml Expose mysql to the internet 2018-11-06 20:58:09 -05:00
docker-entrypoint.sh MAINTAINER is deprecated in Dockerfile. COPY is preferred over ADD in Dockerfile if additional functonality of ADD is not being used. Improved Shebang lines in many files. 2018-10-14 18:00:06 +05:30
Dockerfile Disabling feature that isn't ready yet. 2018-11-06 23:21:25 -05:00
my.cnf moved my.cnf 2018-10-06 15:54:51 -04:00
quick-bootstrap.sh Add todo item for reset switch 2018-11-06 20:58:33 -05:00
README.md We could use more powers (all the sudo's) 2018-11-08 17:06:35 -05:00
start.sh Comment everything and added TODO tags 2018-11-06 16:26:54 -05:00

README.md

Get the lbry-docker repository

sudo git clone https://github.com/lbryio/lbry-docker.git

Setup networking

You only need external networking if you plan on keeping your docker-compose files separate. For the sake of modularity in the design of this git repository the plan is to give you examples to try and then you're supposed to move towards your own custom docker-compose configuration. We're going to create a docker bridge network that is going to be managed externally to your usual docker-compose networks which are compose internal.

docker network create -d bridge --subnet=10.5.1.0/16 lbrynet

Make directories and set permissions

This is only required on host mounted volumes. (the default settings)

sudo mkdir -p ./lbry-docker/lbrycrd/data

sudo chmod -R 755 ./lbry-docker/lbrycrd/data

Setup lbrycrd

cd lbry-docker/lbrycrd

docker-compose up -d && docker-compose logs -f

Wait for lbrycrd to reach the top of the blockchain (console output should noticeably slow down)

Once you've reached the top of the blockchain you can press CTRL+C to exit back to the linux shell.

Setup chainquery

Now that you're done syncing your own copy of the lbry blockchain into the lbrycrd instance you can start spinning up Chainquery and it's dependencies. Since Chainquery is parsing copious amounts of unstructured data stored in the lbry blockchain you have two routes to go.

  1. Route number one [Recommended]: You use some variant of this README.md's instructions to start your chainquery instance using a LBRY.io provided database checkpoint snapshot. This should be basically copy paste-able series of commands to get your own staging instance up asap if you want Route number one, follow along with the rest of this README.md
  2. Route number two: You can your own fresh copy of the chainquery database indexing times may vary from hours to days depending on your hardware.

cd ../chainquery/

./quick-bootstrap.sh getdata

./quick-bootstrap.sh extract

docker-compose.override.yml

Add a PORTS directive for binding chainquery to the host and then run.

./quick-bootstrap.sh start

OR

docker-compose up -d mysql && sleep 30 && docker-compose up -d chainquery