mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-08-19 02:12:23 +00:00
Interim ShyftGeth Docker Complete - PG Docker Complete - Persistent PG Db Storage
This commit is contained in:
David Krett
parent
122c62ca81
commit
3f6f14bc12
5 changed files with 125 additions and 96 deletions
169
README.md
169
README.md
|
|
@ -2,9 +2,7 @@
|
|||
|
||||
Official golang implementation of the Ethereum protocol.
|
||||
|
||||
[](https://godoc.org/github.com/empyrean/go-ethereum)
|
||||
[](https://godoc.org/github.com/empyrean/go-ethereum)
|
||||
[](https://goreportcard.com/report/github.com/empyrean/go-ethereum)
|
||||
[](https://travis-ci.org/ShyftNetwork/shyft_go-ethereum)
|
||||
[](https://gitter.im/ethereum/go-ethereum?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
|
||||
|
|
@ -32,16 +30,16 @@ or, to build the full suite of utilities:
|
|||
|
||||
The go-ethereum project comes with several wrappers/executables found in the `cmd` directory.
|
||||
|
||||
| Command | Description |
|
||||
|:----------:|-------------|
|
||||
| **`geth`** | Our main Ethereum CLI client. It is the entry point into the Ethereum network (main-, test- or private net), capable of running as a full node (default) archive node (retaining all historical state) or a light node (retrieving data live). It can be used by other processes as a gateway into the Ethereum network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. `geth --help` and the [CLI Wiki page](https://github.com/empyrean/go-ethereum/wiki/Command-Line-Options) for command line options. |
|
||||
| `abigen` | Source code generator to convert Ethereum contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain [Ethereum contract ABIs](https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) with expanded functionality if the contract bytecode is also available. However it also accepts Solidity source files, making development much more streamlined. Please see our [Native DApps](https://github.com/empyrean/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts) wiki page for details. |
|
||||
| `bootnode` | Stripped down version of our Ethereum client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks. |
|
||||
| `evm` | Developer utility version of the EVM (Ethereum Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g. `evm --code 60ff60ff --debug`). |
|
||||
| `gethrpctest` | Developer utility tool to support our [ethereum/rpc-test](https://github.com/ethereum/rpc-tests) test suite which validates baseline conformity to the [Ethereum JSON RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC) specs. Please see the [test suite's readme](https://github.com/ethereum/rpc-tests/blob/master/README.md) for details. |
|
||||
| `rlpdump` | Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://github.com/ethereum/wiki/wiki/RLP)) dumps (data encoding used by the Ethereum protocol both network as well as consensus wise) to user friendlier hierarchical representation (e.g. `rlpdump --hex CE0183FFFFFFC4C304050583616263`). |
|
||||
| `swarm` | swarm daemon and tools. This is the entrypoint for the swarm network. `swarm --help` for command line options and subcommands. See https://swarm-guide.readthedocs.io for swarm documentation. |
|
||||
| `puppeth` | a CLI wizard that aids in creating a new Ethereum network. |
|
||||
| Command | Description |
|
||||
| :-----------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| **`geth`** | Our main Ethereum CLI client. It is the entry point into the Ethereum network (main-, test- or private net), capable of running as a full node (default) archive node (retaining all historical state) or a light node (retrieving data live). It can be used by other processes as a gateway into the Ethereum network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. `geth --help` and the [CLI Wiki page](https://github.com/empyrean/go-ethereum/wiki/Command-Line-Options) for command line options. |
|
||||
| `abigen` | Source code generator to convert Ethereum contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain [Ethereum contract ABIs](https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) with expanded functionality if the contract bytecode is also available. However it also accepts Solidity source files, making development much more streamlined. Please see our [Native DApps](https://github.com/empyrean/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts) wiki page for details. |
|
||||
| `bootnode` | Stripped down version of our Ethereum client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks. |
|
||||
| `evm` | Developer utility version of the EVM (Ethereum Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g. `evm --code 60ff60ff --debug`). |
|
||||
| `gethrpctest` | Developer utility tool to support our [ethereum/rpc-test](https://github.com/ethereum/rpc-tests) test suite which validates baseline conformity to the [Ethereum JSON RPC](https://github.com/ethereum/wiki/wiki/JSON-RPC) specs. Please see the [test suite's readme](https://github.com/ethereum/rpc-tests/blob/master/README.md) for details. |
|
||||
| `rlpdump` | Developer utility tool to convert binary RLP ([Recursive Length Prefix](https://github.com/ethereum/wiki/wiki/RLP)) dumps (data encoding used by the Ethereum protocol both network as well as consensus wise) to user friendlier hierarchical representation (e.g. `rlpdump --hex CE0183FFFFFFC4C304050583616263`). |
|
||||
| `swarm` | swarm daemon and tools. This is the entrypoint for the swarm network. `swarm --help` for command line options and subcommands. See https://swarm-guide.readthedocs.io for swarm documentation. |
|
||||
| `puppeth` | a CLI wizard that aids in creating a new Ethereum network. |
|
||||
|
||||
## Running geth
|
||||
|
||||
|
|
@ -63,14 +61,14 @@ $ geth console
|
|||
|
||||
This command will:
|
||||
|
||||
* Start geth in fast sync mode (default, can be changed with the `--syncmode` flag), causing it to
|
||||
download more data in exchange for avoiding processing the entire history of the Ethereum network,
|
||||
which is very CPU intensive.
|
||||
* Start up Geth's built-in interactive [JavaScript console](https://github.com/empyrean/go-ethereum/wiki/JavaScript-Console),
|
||||
(via the trailing `console` subcommand) through which you can invoke all official [`web3` methods](https://github.com/ethereum/wiki/wiki/JavaScript-API)
|
||||
as well as Geth's own [management APIs](https://github.com/empyrean/go-ethereum/wiki/Management-APIs).
|
||||
This too is optional and if you leave it out you can always attach to an already running Geth instance
|
||||
with `geth attach`.
|
||||
- Start geth in fast sync mode (default, can be changed with the `--syncmode` flag), causing it to
|
||||
download more data in exchange for avoiding processing the entire history of the Ethereum network,
|
||||
which is very CPU intensive.
|
||||
- Start up Geth's built-in interactive [JavaScript console](https://github.com/empyrean/go-ethereum/wiki/JavaScript-Console),
|
||||
(via the trailing `console` subcommand) through which you can invoke all official [`web3` methods](https://github.com/ethereum/wiki/wiki/JavaScript-API)
|
||||
as well as Geth's own [management APIs](https://github.com/empyrean/go-ethereum/wiki/Management-APIs).
|
||||
This too is optional and if you leave it out you can always attach to an already running Geth instance
|
||||
with `geth attach`.
|
||||
|
||||
### Full node on the Ethereum test network
|
||||
|
||||
|
|
@ -88,22 +86,22 @@ testnet too. Please see above for their explanations if you've skipped to here.
|
|||
|
||||
Specifying the `--testnet` flag however will reconfigure your Geth instance a bit:
|
||||
|
||||
* Instead of using the default data directory (`~/.ethereum` on Linux for example), Geth will nest
|
||||
itself one level deeper into a `testnet` subfolder (`~/.ethereum/testnet` on Linux). Note, on OSX
|
||||
and Linux this also means that attaching to a running testnet node requires the use of a custom
|
||||
endpoint since `geth attach` will try to attach to a production node endpoint by default. E.g.
|
||||
`geth attach <datadir>/testnet/geth.ipc`. Windows users are not affected by this.
|
||||
* Instead of connecting the main Ethereum network, the client will connect to the test network,
|
||||
which uses different P2P bootnodes, different network IDs and genesis states.
|
||||
- Instead of using the default data directory (`~/.ethereum` on Linux for example), Geth will nest
|
||||
itself one level deeper into a `testnet` subfolder (`~/.ethereum/testnet` on Linux). Note, on OSX
|
||||
and Linux this also means that attaching to a running testnet node requires the use of a custom
|
||||
endpoint since `geth attach` will try to attach to a production node endpoint by default. E.g.
|
||||
`geth attach <datadir>/testnet/geth.ipc`. Windows users are not affected by this.
|
||||
- Instead of connecting the main Ethereum network, the client will connect to the test network,
|
||||
which uses different P2P bootnodes, different network IDs and genesis states.
|
||||
|
||||
*Note: Although there are some internal protective measures to prevent transactions from crossing
|
||||
_Note: Although there are some internal protective measures to prevent transactions from crossing
|
||||
over between the main network and test network, you should make sure to always use separate accounts
|
||||
for play-money and real-money. Unless you manually move accounts, Geth will by default correctly
|
||||
separate the two networks and will not make any accounts available between them.*
|
||||
separate the two networks and will not make any accounts available between them._
|
||||
|
||||
### Full node on the Rinkeby test network
|
||||
|
||||
The above test network is a cross client one based on the ethash proof-of-work consensus algorithm. As such, it has certain extra overhead and is more susceptible to reorganization attacks due to the network's low difficulty / security. Go Ethereum also supports connecting to a proof-of-authority based test network called [*Rinkeby*](https://www.rinkeby.io) (operated by members of the community). This network is lighter, more secure, but is only supported by go-ethereum.
|
||||
The above test network is a cross client one based on the ethash proof-of-work consensus algorithm. As such, it has certain extra overhead and is more susceptible to reorganization attacks due to the network's low difficulty / security. Go Ethereum also supports connecting to a proof-of-authority based test network called [_Rinkeby_](https://www.rinkeby.io) (operated by members of the community). This network is lighter, more secure, but is only supported by go-ethereum.
|
||||
|
||||
```
|
||||
$ geth --rinkeby console
|
||||
|
|
@ -123,7 +121,7 @@ To get an idea how the file should look like you can use the `dumpconfig` subcom
|
|||
$ geth --your-favourite-flags dumpconfig
|
||||
```
|
||||
|
||||
*Note: This works only with geth v1.6.0 and above.*
|
||||
_Note: This works only with geth v1.6.0 and above._
|
||||
|
||||
#### Docker quick start
|
||||
|
||||
|
|
@ -135,7 +133,7 @@ docker run -d --name ethereum-node -v /Users/alice/ethereum:/root \
|
|||
ethereum/client-go
|
||||
```
|
||||
|
||||
This will start geth in fast-sync mode with a DB memory allowance of 1GB just as the above command does. It will also create a persistent volume in your home directory for saving your blockchain as well as map the default ports. There is also an `alpine` tag available for a slim version of the image.
|
||||
This will start geth in fast-sync mode with a DB memory allowance of 1GB just as the above command does. It will also create a persistent volume in your home directory for saving your blockchain as well as map the default ports. There is also an `alpine` tag available for a slim version of the image.
|
||||
|
||||
Do not forget `--rpcaddr 0.0.0.0`, if you want to access RPC from other containers and/or hosts. By default, `geth` binds to the local interface and RPC endpoints is not accessible from the outside.
|
||||
|
||||
|
|
@ -153,19 +151,19 @@ These can be turned on/off and configured as you'd expect.
|
|||
|
||||
HTTP based JSON-RPC API options:
|
||||
|
||||
* `--rpc` Enable the HTTP-RPC server
|
||||
* `--rpcaddr` HTTP-RPC server listening interface (default: "localhost")
|
||||
* `--rpcport` HTTP-RPC server listening port (default: 8545)
|
||||
* `--rpcapi` API's offered over the HTTP-RPC interface (default: "eth,net,web3")
|
||||
* `--rpccorsdomain` Comma separated list of domains from which to accept cross origin requests (browser enforced)
|
||||
* `--ws` Enable the WS-RPC server
|
||||
* `--wsaddr` WS-RPC server listening interface (default: "localhost")
|
||||
* `--wsport` WS-RPC server listening port (default: 8546)
|
||||
* `--wsapi` API's offered over the WS-RPC interface (default: "eth,net,web3")
|
||||
* `--wsorigins` Origins from which to accept websockets requests
|
||||
* `--ipcdisable` Disable the IPC-RPC server
|
||||
* `--ipcapi` API's offered over the IPC-RPC interface (default: "admin,debug,eth,miner,net,personal,shh,txpool,web3")
|
||||
* `--ipcpath` Filename for IPC socket/pipe within the datadir (explicit paths escape it)
|
||||
- `--rpc` Enable the HTTP-RPC server
|
||||
- `--rpcaddr` HTTP-RPC server listening interface (default: "localhost")
|
||||
- `--rpcport` HTTP-RPC server listening port (default: 8545)
|
||||
- `--rpcapi` API's offered over the HTTP-RPC interface (default: "eth,net,web3")
|
||||
- `--rpccorsdomain` Comma separated list of domains from which to accept cross origin requests (browser enforced)
|
||||
- `--ws` Enable the WS-RPC server
|
||||
- `--wsaddr` WS-RPC server listening interface (default: "localhost")
|
||||
- `--wsport` WS-RPC server listening port (default: 8546)
|
||||
- `--wsapi` API's offered over the WS-RPC interface (default: "eth,net,web3")
|
||||
- `--wsorigins` Origins from which to accept websockets requests
|
||||
- `--ipcdisable` Disable the IPC-RPC server
|
||||
- `--ipcapi` API's offered over the IPC-RPC interface (default: "admin,debug,eth,miner,net,personal,shh,txpool,web3")
|
||||
- `--ipcpath` Filename for IPC socket/pipe within the datadir (explicit paths escape it)
|
||||
|
||||
You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect
|
||||
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)
|
||||
|
|
@ -189,20 +187,22 @@ and agree upon. This consists of a small JSON file (e.g. call it `genesis.json`)
|
|||
```json
|
||||
{
|
||||
"config": {
|
||||
"chainId": 0,
|
||||
"homesteadBlock": 0,
|
||||
"eip155Block": 0,
|
||||
"eip158Block": 0
|
||||
},
|
||||
"alloc" : {},
|
||||
"coinbase" : "0x0000000000000000000000000000000000000000",
|
||||
"difficulty" : "0x20000",
|
||||
"extraData" : "",
|
||||
"gasLimit" : "0x2fefd8",
|
||||
"nonce" : "0x0000000000000042",
|
||||
"mixhash" : "0x0000000000000000000000000000000000000000000000000000000000000000",
|
||||
"parentHash" : "0x0000000000000000000000000000000000000000000000000000000000000000",
|
||||
"timestamp" : "0x00"
|
||||
"chainId": 0,
|
||||
"homesteadBlock": 0,
|
||||
"eip155Block": 0,
|
||||
"eip158Block": 0
|
||||
},
|
||||
"alloc": {},
|
||||
"coinbase": "0x0000000000000000000000000000000000000000",
|
||||
"difficulty": "0x20000",
|
||||
"extraData": "",
|
||||
"gasLimit": "0x2fefd8",
|
||||
"nonce": "0x0000000000000042",
|
||||
"mixhash":
|
||||
"0x0000000000000000000000000000000000000000000000000000000000000000",
|
||||
"parentHash":
|
||||
"0x0000000000000000000000000000000000000000000000000000000000000000",
|
||||
"timestamp": "0x00"
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -228,7 +228,8 @@ $ geth init path/to/genesis.json
|
|||
#### Creating the rendezvous point
|
||||
|
||||
With all nodes that you want to run initialized to the desired genesis state, you'll need to start a
|
||||
bootstrap node that others can use to find each other in your network and/or over the internet. The
|
||||
bootstrap node that others can use to find each other in your
|
||||
network and/or over the internet. The
|
||||
clean way is to configure and run a dedicated bootnode:
|
||||
|
||||
```
|
||||
|
|
@ -241,7 +242,7 @@ that other nodes can use to connect to it and exchange peer information. Make su
|
|||
displayed IP address information (most probably `[::]`) with your externally accessible IP to get the
|
||||
actual `enode` URL.
|
||||
|
||||
*Note: You could also use a full fledged Geth node as a bootnode, but it's the less recommended way.*
|
||||
_Note: You could also use a full fledged Geth node as a bootnode, but it's the less recommended way._
|
||||
|
||||
#### Starting up your member nodes
|
||||
|
||||
|
|
@ -254,8 +255,8 @@ private network separated, so do also specify a custom `--datadir` flag.
|
|||
$ geth --datadir=path/to/custom/data/folder --bootnodes=<bootnode-enode-url-from-above>
|
||||
```
|
||||
|
||||
*Note: Since your network will be completely cut off from the main and test networks, you'll also
|
||||
need to configure a miner to process transactions and create new blocks for you.*
|
||||
_Note: Since your network will be completely cut off from the main and test networks, you'll also
|
||||
need to configure a miner to process transactions and create new blocks for you._
|
||||
|
||||
#### Running a private miner
|
||||
|
||||
|
|
@ -280,12 +281,34 @@ limit blocks converge to (`--targetgaslimit`) and the price transactions are acc
|
|||
## SHYFT NOTES
|
||||
|
||||
#### CLI
|
||||
|
||||
Run `./shyft-geth.sh` with one of the following flags:
|
||||
|
||||
- `--setup` - Setups postgres and the shyft chain db.
|
||||
- `--start` - Starts geth.
|
||||
- `--reset` - Drops postgress and chain db, and reinstantiates both.
|
||||
- `--js [web3 filename]` - Executes web3 calls with a passed file name. If the file name is `sendTransactions.js`, `./shyft-geth.sh --js sendTransactions`.
|
||||
- `--setup` - Setups postgres and the shyft chain db.
|
||||
- `--start` - Starts geth.
|
||||
- `--reset` - Drops postgress and chain db, and reinstantiates both.
|
||||
- `--js [web3 filename]` - Executes web3 calls with a passed file name. If the file name is `sendTransactions.js`, `./shyft-geth.sh --js sendTransactions`.
|
||||
|
||||
#### Docker Images
|
||||
|
||||
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/).
|
||||
|
||||
To launch ShyftGeth and PG - issue the following command from the root of the project directory:
|
||||
|
||||
`docker-compose up`
|
||||
|
||||
If you would like to reinitialize/rebuild the docker images you can issue the following command:
|
||||
|
||||
`docker-compose up --build`
|
||||
|
||||
The Postgresql Database Container will persist the database data to the the pg-data/ directory. So if you do want to reinitialize the database you should delete the content of this directory prior to launching the docker containers. From your local machine you can view the database by connecting to the database in the container at 127.0.0.1:8001
|
||||
|
||||
_TODO_
|
||||
|
||||
- Dockerize shyftBlockExplorerAPI
|
||||
- Dockerize shyftBlockExplorerUI
|
||||
- Adjust docker scripts and ports to facilitate sending of test transactions
|
||||
- Modify Docker scripts to facilitate hot reloading during development
|
||||
|
||||
## Contribution
|
||||
|
||||
|
|
@ -301,11 +324,11 @@ procedures quick and simple.
|
|||
|
||||
Please make sure your contributions adhere to our coding guidelines:
|
||||
|
||||
* Code must adhere to the official Go [formatting](https://golang.org/doc/effective_go.html#formatting) guidelines (i.e. uses [gofmt](https://golang.org/cmd/gofmt/)).
|
||||
* Code must be documented adhering to the official Go [commentary](https://golang.org/doc/effective_go.html#commentary) guidelines.
|
||||
* Pull requests need to be based on and opened against the `master` branch.
|
||||
* Commit messages should be prefixed with the package(s) they modify.
|
||||
* E.g. "eth, rpc: make trace configs optional"
|
||||
- Code must adhere to the official Go [formatting](https://golang.org/doc/effective_go.html#formatting) guidelines (i.e. uses [gofmt](https://golang.org/cmd/gofmt/)).
|
||||
- Code must be documented adhering to the official Go [commentary](https://golang.org/doc/effective_go.html#commentary) guidelines.
|
||||
- Pull requests need to be based on and opened against the `master` branch.
|
||||
- Commit messages should be prefixed with the package(s) they modify.
|
||||
- E.g. "eth, rpc: make trace configs optional"
|
||||
|
||||
Please see the [Developers' Guide](https://github.com/empyrean/go-ethereum/wiki/Developers'-Guide)
|
||||
for more details on configuring your environment, managing project dependencies and testing procedures.
|
||||
|
|
|
|||
|
|
@ -4,6 +4,5 @@ FROM postgres:10.4-alpine
|
|||
WORKDIR /
|
||||
COPY ./shyft-cli/postgres_setup/docker_init_user_db.sh /docker-entrypoint-initdb.d/docker_init_user_db.sh
|
||||
RUN cd /docker-entrypoint-initdb.d && ls -a
|
||||
|
||||
|
||||
VOLUME ["/var/lib/postgresql"]
|
||||
EXPOSE 5432
|
||||
|
|
@ -0,0 +1,19 @@
|
|||
FROM golang:1.10.3-alpine
|
||||
|
||||
COPY ./shyftBlockExplorerApi /go/src/github.com/ShyftNetwork/go-empyrean/shyftBlockExplorerApi
|
||||
# COPY ./vendor /go/src/github.com/ShyftNetwork/go-empyrean/vendor
|
||||
COPY ./core /go/src/github.com/ShyftNetwork/go-empyrean/core
|
||||
# COPY ./common /go/src/github.com/ShyftNetwork/go-empyrean/common
|
||||
COPY .git /go/src/github.com/ShyftNetwork/go-empyrean/.git
|
||||
|
||||
|
||||
WORKDIR /go/src/github.com/ShyftNetwork/go-empyrean/shyftBlockExplorerApi
|
||||
|
||||
RUN apk add --update git make gcc musl-dev linux-headers ca-certificates
|
||||
RUN go get ./
|
||||
|
||||
RUN go build
|
||||
|
||||
CMD go get github.com/pilu/fresh && fresh
|
||||
|
||||
EXPOSE 8080
|
||||
|
|
@ -8,10 +8,7 @@ RUN \
|
|||
apk add --update git make gcc musl-dev linux-headers ca-certificates && \
|
||||
(cd /go/src/github.com/ShyftEthereum/go-empyrean && make geth) && \
|
||||
cp -v /go/src/github.com/ShyftEthereum/go-empyrean/build/bin/geth /bin
|
||||
COPY ./shyft-cli/initShyftGeth.sh /
|
||||
COPY ./shyft-cli/resetShyftGeth.sh /
|
||||
COPY ./shyft-cli/startShyftGeth.sh /
|
||||
# COPY ./containers/docker/develop-alpine/shyftGeth/wait-for-postgres.sh /
|
||||
|
||||
COPY config.toml /
|
||||
COPY unlockPasswords.txt /
|
||||
COPY ShyftNetwork.json /
|
||||
|
|
@ -22,6 +19,6 @@ COPY UTC--2018-03-18T22-37-04.212101982Z--5bd738164c61fb50eb12e227846cbaef2de965
|
|||
COPY UTC--2018-03-18T22-37-12.082606217Z--c04ee4131895f1d0c294d508af65d94060aa42bb /
|
||||
COPY UTC--2018-03-18T22-37-19.650676366Z--07d899c4ac0c1725c35c5f816e60273b33a964f7 /
|
||||
|
||||
WORKDIR /
|
||||
WORKDIR /go/src/github.com/ShyftEthereum/go-empyrean
|
||||
|
||||
CMD ["./initShyftGeth.sh", "/go/src/ShyftNetwork/go-empyrean/shyft-cli/initShyftGeth.sh/startShyftGeth.sh"]
|
||||
CMD ["./shyft-cli/initShyftGeth.sh", "./shyft-cli/startShyftGeth.sh"]
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ services:
|
|||
- "30301:30301"
|
||||
- "30303:30303/udp"
|
||||
- "30304:30304"
|
||||
- "5432:5432"
|
||||
volumes:
|
||||
- .:/go/src/ShyftNetwork/go-empyrean
|
||||
working_dir: /go/src/ShyftNetwork/go-empyrean
|
||||
|
|
@ -20,16 +19,17 @@ services:
|
|||
networks:
|
||||
- shyftnet
|
||||
command: >
|
||||
sh -c '/go/src/ShyftNetwork/go-empyrean/wait-for.sh pg:5432 &&
|
||||
sh -c 'cd /go/src/ShyftNetwork/go-empyrean &&
|
||||
./wait-for.sh pg:5432 &&
|
||||
DBENV=docker export DBENV &&
|
||||
/initShyftGeth.sh &&
|
||||
/startShyftGeth.sh'
|
||||
./shyft-cli/initShyftGeth.sh &&
|
||||
./shyft-cli/startShyftGeth.sh'
|
||||
pg:
|
||||
build:
|
||||
context: $PWD
|
||||
dockerfile: containers/docker/develop-alpine/pg/Dockerfile
|
||||
volumes:
|
||||
- ./pg-data:/var/lib/postgresql/
|
||||
- ./pg-data:/var/lib/postgresql/data
|
||||
ports:
|
||||
- "8001:5432"
|
||||
networks:
|
||||
|
|
@ -41,18 +41,9 @@ services:
|
|||
# build:
|
||||
# context: $PWD
|
||||
# dockerfile: containers/docker/develop-alpine/shyftApi/Dockerfile
|
||||
# volumes: -
|
||||
|
||||
|
||||
|
||||
networks:
|
||||
shyftnet:
|
||||
driver: bridge
|
||||
# volumes:
|
||||
# pg-data:
|
||||
|
||||
# api:
|
||||
# build:
|
||||
# context: ./containers/docker/develop-alpine/shyftApi
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue