You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ Here's a breakdown of the key variables:
89
89
Defines how the Auto Upgrader runs. Options are `process`, `service`, or `docker`. Default is `service`.
90
90
91
91
-**SUBVORTEX_PRERELEASE_TYPE**:
92
-
Specifies a single prerelease identifier you want to be notified about. Options are `alpha` or `rc` (**use ONLY in TESTNET**). Remove this variable to receive notifications from `latest` (**use in MAINNET**) prerelease types. Default is an empty string, which disables prerelease notifications.
92
+
Specifies a single prerelease identifier you want to be notified about. Options are `alpha`(**use ONLY in DEVNET**) or `rc` (**use ONLY in TESTNET**). Remove this variable to receive notifications from `latest` (**use in MAINNET**) prerelease types. Default is an empty string, which disables prerelease notifications.
93
93
94
94
-**SUBVORTEX_EXECUTION_ROLE**:
95
95
Specifies the type of neuron running on this machine. Options are `miner` and `validator`. Default value is `miner`. The Auto Upgrader uses this to decide how the machine should upgrade.
@@ -154,7 +154,7 @@ Use `-h` to see the options
154
154
155
155
# 🔄 Quick Upgrade <aid="quick-upgrade"></a>
156
156
157
-
To upgrade the Auto Upgrade when a new release has been deployed, you can run
157
+
To upgrade the Auto Upgrader when a new release has been deployed, you can run
0 commit comments