Minor improvements to operator setup instructions (#111)

* docs: Add container pull to operator setup final step * docs: Improve register_operator_on_setup description
Nuffle-Labs · Apr 23, 2024 · b07613c · b07613c
1 parent d4aeab6
commit b07613c
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 4 deletions.
diff --git a/docs/docs/operator/setup.md b/docs/docs/operator/setup.md
@@ -131,8 +131,10 @@ enable_metrics: true
 node_api_ip_port_address: near-sffl-operator:9010
 enable_node_api: true
 
-# Whether to try and register the operator in the AVS and in EL on startup
-# If set, it will not re-register the operator if already registered
+# Whether to try and register the operator in the AVS and in EL on startup.
+# It will not re-register the operator if already registered.
+# If unset, the operator will not be registered on startup! You'll need to
+# manually register the operator - not recommended
 register_operator_on_startup: true
 
 # RMQ address and indexer rollup IDs
@@ -207,6 +209,7 @@ This is the final step!
 Stop the previous execution with `Ctrl+C`. Then, run the following:
 ```
 source .env
+docker compose --profile indexer --profile operator pull
 docker compose --profile indexer --profile operator up
 ```
 

diff --git a/setup/operator/config/operator.yaml b/setup/operator/config/operator.yaml
@@ -28,8 +28,10 @@ enable_metrics: true
 node_api_ip_port_address: 0.0.0.0:9010
 enable_node_api: true
 
-# Whether to try and register the operator in the AVS and in EL on startup
-# If set, it will not re-register the operator if already registered
+# Whether to try and register the operator in the AVS and in EL on startup.
+# It will not re-register the operator if already registered.
+# If unset, the operator will not be registered on startup! You'll need to
+# manually register the operator - not recommended
 register_operator_on_startup: true
 
 # RMQ address and indexer rollup IDs