You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building geth requires both a Go (version 1.7 or later) and a C compiler.
267
+
Building geth requires both a Go (version 1.9 or later) and a C compiler.
267
268
You can install them using your favourite package manager.
268
269
Once the dependencies are installed, run
269
270
@@ -413,7 +414,7 @@ HTTP based JSON-RPC API options:
413
414
-`--ipcpath` Filename for IPC socket/pipe within the datadir (explicit paths escape it)
414
415
415
416
You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect
416
-
via HTTP, WS or IPC to a Geth node configured with the above flags and you'll need to speak [JSON-RPC](http://www.jsonrpc.org/specification)
417
+
via HTTP, WS or IPC to a Geth node configured with the above flags and you'll need to speak [JSON-RPC](https://www.jsonrpc.org/specification)
417
418
on all transports. You can reuse the same connection for multiple requests!
418
419
419
420
**Note: Please understand the security implications of opening up an HTTP/WS based transport before
@@ -525,6 +526,77 @@ Which will start mining blocks and transactions on a single CPU thread, creditin
525
526
the account specified by `--etherbase`. You can further tune the mining by changing the default gas
526
527
limit blocks converge to (`--targetgaslimit`) and the price transactions are accepted at (`--gasprice`).
527
528
529
+
## SHYFT NOTES
530
+
531
+
#### CLI
532
+
533
+
Run `./shyft-geth.sh` with one of the following flags:
534
+
535
+
-`--setup` - Setups postgres and the shyft chain db.
536
+
-`--start` - Starts geth.
537
+
-`--reset` - Drops postgress and chain db, and reinstantiates both.
538
+
-`--js [web3 filename]` - Executes web3 calls with a passed file name. If the file name is `sendTransactions.js`, `./shyft-geth.sh --js sendTransactions`.
539
+
540
+
#### Docker Images
541
+
542
+
Docker Images are available for ShyftGeth and the Postgresql Database which can be used for development and testing. To launch these containers you will need to have docker-compose installed on your computer. Installation instructions for docker-compose are available [here](https://docs.docker.com/install/).
543
+
544
+
To launch ShyftGeth, PG, the ShyftBlock Explorer Api and UI - issue the following command from the root of the project directory:
545
+
546
+
`docker-compose up`
547
+
548
+
If you would like to reinitialize/rebuild the docker images you can issue the following command:
549
+
550
+
`docker-compose up --build`
551
+
552
+
To rebuild any one of the services - issue the following commands:
553
+
554
+
```
555
+
docker-compose up -d --no-deps --build <docker compose file service name>
556
+
557
+
# ie. for shyftBlockExplorerApi:
558
+
# docker-compose up -d --no-deps --build shyft_block_api
559
+
```
560
+
__The Postgresql Database Container will persist the database data to a folder in the root of the project directory - pg-data" __. So if you do want to reinitialize the database you should delete this docker container prior to launching the docker containers. To delete this docker volume and have it recreated you should input the following command:
561
+
562
+
```docker volume rm go-empyrean_pg-data```
563
+
564
+
From your local machine you can view the database by connecting to the database in the container at 127.0.0.1:8001. To access the shyftBlockExplorer open a browser and visit http://localhost:3000
565
+
566
+
__Blockchain data is persisted to ./ethash/.ethash__ and ./shyftData. If you would like to reset the test blockchain you will need to delete the ./ethash and ./shyftData directories.
567
+
568
+
The docker container for the ShyftBlockExplorerApi utilizes govendor to minimize its image size. __If you would like the docker image for this container to reflect any uncommitted changes which may have occurred in the go-empyrean repository, ie. changes with respect to go-empyrean core (ie. cryptographic functions and database). Prior to launching the docker containers you should rebuild the vendor directory for the shyftBlockExplorerApi - by executing the following steps:__
569
+
570
+
```
571
+
# remove existing shyftBlockExplorerApi vendor.json and vendored components:
572
+
573
+
rm -rf shyftBlockExplorerApi/vendor
574
+
575
+
# reinitialize vendor.json
576
+
577
+
cd shyftBlockExplorerApi && govendor init
578
+
579
+
# rebuild vendor.json using latest uncommitted changes
580
+
581
+
govendor add -tree -uncommitted +external
582
+
583
+
# due to a bug in govendor and it not being able to pull in some dependencies that are c-header files
584
+
# you should execute the following commands - see these issues - which whilst closed
585
+
# appears to have not been fixed: https://github.com/kardianos/govendor/issues/124 && https://github.com/kardianos/govendor/issues/61
0 commit comments