Skip to content
Snippets Groups Projects
Commit 0d12e06f authored by Florent Gluck's avatar Florent Gluck
Browse files

Updated README.md with production server info

parent 217f7a3f
No related branches found
No related tags found
No related merge requests found
...@@ -45,9 +45,9 @@ Both clients feature the same commands and they are available for multiples oper ...@@ -45,9 +45,9 @@ Both clients feature the same commands and they are available for multiples oper
| OSX | ARM64 | binaries/arm64/darwin | | OSX | ARM64 | binaries/arm64/darwin |
| Windows | ARM64 | binaries/arm64/windows | | Windows | ARM64 | binaries/arm64/windows |
Because communication between client and server is encrypted, a public certificate is required. It is available in the `certificate` directory: Because communication between client and server is encrypted, a public certificate is required. It is available in the `certificates` directory:
- `ca-cert.isc-nexus-dev.pem` - `ca-cert.isc-nexus-prod.pem`
## Running nexus-client ## Running nexus-client
...@@ -64,16 +64,16 @@ Details of the server and certificate to use at ISC are shown below: ...@@ -64,16 +64,16 @@ Details of the server and certificate to use at ISC are shown below:
| | | | | |
|--- |--- | |--- |--- |
| `10.136.26.125:1077` | ip and port of the server to use | | `10.136.26.127:1077` | ip and port of the server to use |
| `ca-cert.isc-nexus-dev.pem` | public certificate to use | | `ca-cert.isc-nexus-prod.pem` | public certificate to use |
On Linux and OSX, a simple and effective way is to store these variables in a `.env` file that is sourced before running the clients. On Linux and OSX, a simple and effective way is to store these variables in a `.env` file that is sourced before running the clients.
For instance, create `.env.nexus` with the following content: For instance, create `.env.nexus` with the following content:
``` ```
export NEXUS_SERVER=10.136.26.125:1077 export NEXUS_SERVER=10.136.26.127:1077
export NEXUS_CERT=$(pwd)/ca-cert.isc-nexus-dev.pem export NEXUS_CERT=$(pwd)/ca-cert.isc-nexus-prod.pem
``` ```
Then, source it and run your client of choice: Then, source it and run your client of choice:
...@@ -389,8 +389,8 @@ vmstart 6713ce26-941e-4d95-8e92-6b71d44bf75a ...@@ -389,8 +389,8 @@ vmstart 6713ce26-941e-4d95-8e92-6b71d44bf75a
Example of variables initialization: Example of variables initialization:
``` ```
export NEXUS_SERVER=192.168.1.25 export NEXUS_SERVER=10.136.26.127:1077
export NEXUS_CERT=/home/janedoe/ca-cert.isc-nexus-dev.pem export NEXUS_CERT=$(pwd)/ca-cert.isc-nexus-prod.pem
``` ```
Below is a screenshot of `nexus-exam`'s graphical interface: Below is a screenshot of `nexus-exam`'s graphical interface:
...@@ -406,9 +406,8 @@ First, you need to create the VM that will be used by the students during the ex ...@@ -406,9 +406,8 @@ First, you need to create the VM that will be used by the students during the ex
1. First, authenticate onto the nexus server (make sure the `NEXUS_SERVER` and `NEXUS_CERT` environment variables are properly initialized): 1. First, authenticate onto the nexus server (make sure the `NEXUS_SERVER` and `NEXUS_CERT` environment variables are properly initialized):
``` ```
export NEXUS_SERVER=192.168.1.25:1077 export NEXUS_SERVER=10.136.26.127:1077
export NEXUS_CERT=/home/janedoe/ca-cert.isc-nexus-dev.pem export NEXUS_CERT=$(pwd)/ca-cert.isc-nexus-prod.pem
./nexush janedoe@nexus.org ./nexush janedoe@nexus.org
``` ```
After entering your password, you should see: After entering your password, you should see:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment