StakeSquid/dshackle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

solution: paths relative to config, default is at /etc/dshackle

Browse Source
This commit is contained in:
Igor Artamonov
2019-09-08 22:30:46 -04:00
parent 26d2b0a3a0
commit 7fd27d581a
11 changed files with 207 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/02-quick-start.adoc
View File

@@ -71,7 +71,7 @@ export INFURA_USER=...
.Run Dshackle
[source,bash]
----
docker run -p 2449:2449 -v $(pwd):/config -w /config -e "INFURA_USER=$INFURA_USER" emeraldpay/dshackle
docker run -p 2449:2449 -v $(pwd):/etc/dshackle -e "INFURA_USER=$INFURA_USER" emeraldpay/dshackle
----
.Connect and listen for new blocks on Ethereum Mainnet

12
docs/03-server-config.adoc
View File

@@ -1,6 +1,10 @@
== Server Configuration
Dshackle server tries to load its configuration from `/etc/dshackle/dshackle.yaml`, if it can't find a file at that path
it tries to load file `dshackle.yaml` from current working directory. If none of them found server fails to run with an error.
[source,yaml]
.Example dshackle.yaml configuration:
----
version: v1
port: 2449
@@ -16,10 +20,10 @@ upstreams:
config: "upstreams.yaml"
----
Configures following:
It configures following:
- server is listening on `0.0.0.0:2449`
- TLS is enabled
- server certificate in located at `server.crt` with key for it at `server.p8.key`
- server requires a client authentication by TLS client certificate signed by `ca.crt` certificate
- upstreams configuration is configured in file `upstreams.yaml`
- server certificate is located at `server.crt` with the key for it at `server.p8.key`
- the server requires a client authentication by TLS client certificate signed by `ca.crt` certificate
- upstreams configuration is configured in the file `upstreams.yaml`