Updated docs

Author: jclapis

docs/docs/get_started/building.md

@@ -166,7 +166,6 @@ This will create a binary in `./target/release/commit-boost-signer`. To verify i
 The signer needs the following environment variables set:
 - `CB_CONFIG` = path of your config file.
 - `CB_JWTS` = a dummy key-value pair of [JWT](https://en.wikipedia.org/wiki/JSON_Web_Token) values for various services. Since we don't need them for the sake of just testing the binary, we can use something like `"test_jwts=dummy"`.
-- `CB_SIGNER_PORT` = the network port to listen for signer requests on. Default is `20000`.
 
 Set these values, create the `keys` and `secrets` directories listed in the configuration file, and run the binary:
 

docs/docs/get_started/configuration.md

@@ -39,6 +39,13 @@ Commit-Boost supports both local and remote signers. The signer module is respon
 To start a local signer module, you need to include its parameters in the config file
 
 ```toml
+[pbs]
+...
+with_signer = true
+
+[signer]
+port = 20000
+
 [signer.local.loader]
 format = "lighthouse"
 keys_path = "/path/to/keys"
@@ -64,6 +71,10 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
 
   #### Config:
   ```toml
+  [pbs]
+  ...
+  with_signer = true
+
   [signer]
   port = 20000
 
@@ -89,7 +100,13 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
 
   #### Config:
   ```toml
+  [pbs]
+  ...
+  with_signer = true
+
   [signer]
+  port = 20000
+
   [signer.local.loader]
   format = "prysm"
   keys_path = "wallet/direct/accounts/all-accounts.keystore.json"
@@ -112,6 +129,10 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
 
   #### Config:
   ```toml
+  [pbs]
+  ...
+  with_signer = true
+
   [signer]
   port = 20000
 
@@ -136,6 +157,10 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
 
   #### Config:
   ```toml
+  [pbs]
+  ...
+  with_signer = true
+
   [signer]
   port = 20000