Skip to content

Commit

Permalink
docs: update nomad/README file (#323)
Browse files Browse the repository at this point in the history
  • Loading branch information
mrekucci authored Aug 8, 2024
1 parent fa9f3f5 commit 5229cba
Showing 1 changed file with 19 additions and 2 deletions.
21 changes: 19 additions & 2 deletions infrastructure/nomad/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,14 +107,31 @@ For detailed usage instructions on how to use the script, run the following comm
./cluster.sh --help
```

Example of initializing Nomad cluster:
```shell
./cluster.sh init
```

> The `init` should be run only once, before deploying the Nomad cluster.
Example of destroying running Nomad cluster:
```shell
./cluster.sh destroy
```

Example of deploying Nomad cluster:
```shell
./cluster.sh deploy --no-logs-collection --datadog-key <DATADOG_API_KEY>` --l1-rpc-url <L1_RPC_URL>
./cluster.sh deploy --no-logs-collection --datadog-key <DATADOG_API_KEY> --l1-rpc-url <L1_RPC_URL>
```

> After successful deployment, you can find all secrets at: http://<TARGET_MACHINE_IP>:1111/secrets.json
> If only artifacts for a particular architecture and operating system are needed, you
> can specify them using the following environment variables ARTIFACTS_GOOS and ARTIFACTS_GOARCH, respectively.
> This will reduce the number of artifacts generated and thus reduce deployment time.
>
> Example:
> ```shell
> export ARTIFACTS_GOOS=linux
> export ARTIFACTS_GOARCH=amd64
> ```
> After successful deployment, you can find all artifacts (including secrets in the secrets.json file) at: http://<TARGET_MACHINE_IP>:1111

0 comments on commit 5229cba

Please sign in to comment.