Refactor .envs

Author: KaloyanTanev

.env.sample.holesky

@@ -4,17 +4,22 @@
 # Overrides network for all the relevant services.
 NETWORK=holesky
 
-# These profiles dictate what client types to start for execution, consensus, validator and mev clients.
+# Execution layer client to be used in a DV setup.
+# Available options are: nethermind.
 EL=nethermind
-#EL=geth
+# Consensus layer client to be used in a DV setup.
+# Available options are: lighthouse, grandine.
 CL=lighthouse
-#CL=grandine
+# Distributed validator client to be used in a DV setup.
+# Available options are: charon.
 DV=charon
-#DV=charon
+# Validator client to be used in a DV setup.
+# Available options are: lodestar.
 VC=lodestar
-#VC=nimbus
+# MEV client to be used in a DV setup.
+# Available options are: mevboost.
 MEV=mevboost
-#MEV=commitboost
+# Do not edit. These profiles and files dictate Docker what client types to start for execution, consensus, validator and mev clients, which are specified above.
 COMPOSE_PROFILES=el_${EL},cl_${CL},dv_${DV},vc_${VC},mev_${MEV}
 COMPOSE_FILE=compose-el.yml:compose-cl.yml:compose-vc.yml:compose-mev.yml:docker-compose.yml
 

.env.sample.hoodi

@@ -4,17 +4,22 @@
 # Overrides network for all the relevant services.
 NETWORK=hoodi
 
-# These profiles dictate what client types to start for execution, consensus, validator and mev clients.
+# Execution layer client to be used in a DV setup.
+# Available options are: nethermind.
 EL=nethermind
-#EL=geth
+# Consensus layer client to be used in a DV setup.
+# Available options are: lighthouse, grandine.
 CL=lighthouse
-#CL=grandine
+# Distributed validator client to be used in a DV setup.
+# Available options are: charon.
 DV=charon
-#DV=charon
+# Validator client to be used in a DV setup.
+# Available options are: lodestar.
 VC=lodestar
-#VC=nimbus
+# MEV client to be used in a DV setup.
+# Available options are: mevboost.
 MEV=mevboost
-#MEV=commitboost
+# Do not edit. These profiles and files dictate Docker what client types to start for execution, consensus, validator and mev clients, which are specified above.
 COMPOSE_PROFILES=el_${EL},cl_${CL},dv_${DV},vc_${VC},mev_${MEV}
 COMPOSE_FILE=compose-el.yml:compose-cl.yml:compose-vc.yml:compose-mev.yml:docker-compose.yml
 

.env.sample.mainnet

@@ -4,17 +4,22 @@
 # Overrides network for all the relevant services.
 NETWORK=mainnet
 
-# These profiles dictate what client types to start for execution, consensus, validator and mev clients.
+# Execution layer client to be used in a DV setup.
+# Available options are: nethermind.
 EL=nethermind
-#EL=geth
+# Consensus layer client to be used in a DV setup.
+# Available options are: lighthouse, grandine.
 CL=lighthouse
-#CL=grandine
+# Distributed validator client to be used in a DV setup.
+# Available options are: charon.
 DV=charon
-#DV=charon
+# Validator client to be used in a DV setup.
+# Available options are: lodestar.
 VC=lodestar
-#VC=nimbus
+# MEV client to be used in a DV setup.
+# Available options are: mevboost.
 MEV=mevboost
-#MEV=commitboost
+# Do not edit. These profiles and files dictate Docker what client types to start for execution, consensus, validator and mev clients, which are specified above.
 COMPOSE_PROFILES=el_${EL},cl_${CL},dv_${DV},vc_${VC},mev_${MEV}
 COMPOSE_FILE=compose-el.yml:compose-cl.yml:compose-vc.yml:compose-mev.yml:docker-compose.yml