GRIN/nym
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

syntax fix (#4653)

Browse Source
This commit is contained in:
import this
2024-06-14 13:06:15 +00:00
committed by GitHub
parent e8540c13a5
commit 8585a68d7f
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/operators/src/release-cycle.md
+7 -7
View File
@@ -13,13 +13,13 @@ The core team therefore established a flow with different environments:
Frequency of releases to mainnet is aimed to be every ~14 days. This time time window is an optimal compromise between periodicity and qualty assurance/testing, key factors playing an essential role in the development.
| **Stage** | **Environment** | **Branch** | **Ownership |
| :-- | :-- | :-- | :-- |
| development work | local/canary | feature branches | devs |
| cut and test release | canary | release branch | QA |
| bug fixing | canary | directly on release branch | QA & devs |
| put release on sandbox | sandbox | release -> master/develop | QA |
| promote release to mainnet after 3-5 days | mainnet | master | QA |
| **Stage** | **Environment** | **Branch** | **Ownership** |
| :-- | :-- | :-- | :-- |
| development work | local/canary | feature branches | devs |
| cut and test release | canary | release branch | QA |
| bug fixing | canary | directly on release branch | QA & devs |
| put release on sandbox | sandbox | release -> master/develop | QA |
| promote release to mainnet after 3-5 days | mainnet | master | QA |
```ascii
▲ ▲
documentation/operators/src/sandbox.md
+3 -3
View File
@@ -18,13 +18,13 @@ To run Nym binaries in Sandbox Testnet you need to get the `.env` configuration
curl -o sandbox.env -L https://raw.githubusercontent.com/nymtech/nym/develop/envs/sandbox.env
```
2. Run your `nym-node` with all the commands as always with an additional flag `-c` or `--config-env-file` with a path to `sanbox.env` file. For example:
2. Run your `nym-node` with an additional flag `-c` or `--config-env-file` with a path to `sanbox.env` file followed by all needed commands and options. For example:
```sh
# this example is for mixnode mode
./nym-node run --mode mixnode --config-env-file <PATH/TO/sandbox.env>
./nym-node --config-env-file <PATH/TO/>sandbox.env run --mode mixnode
# this example is for exit-gateway mode
./nym-node run --mode exit-gateway --id <ID> --config-env-file <PATH/TO/sandbox.env> --public-ips "$(curl -4 https://ifconfig.me)" --hostname "<YOUR_DOMAIN>" --http-bind-address 0.0.0.0:8080 --mixnet-bind-address 0.0.0.0:1789 true --location <COUNTRY_FULL_NAME>
./nym-node --config-file-env <PATH/TO/>sandbox.env run --mode exit-gateway --id <ID> --public-ips "$(curl -4 https://ifconfig.me)" --hostname "<YOUR_DOMAIN>" --http-bind-address 0.0.0.0:8080 --mixnet-bind-address 0.0.0.0:1789 true --location <COUNTRY_FULL_NAME>
```
3. Bond your node to Nym Sandbox environment: