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
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,14 +91,24 @@ To run the gateway in a prod environment with Docker Compose, follow these steps
91
91
92
92
2. To run the [docker-compose-prod.yml](./docker-compose-prod.yml) file you need a public domain (that you will put in the `DOMAIN_NAME` environment variable) and a TLS certificate for that domain (because it is configured to make the gateway run with TLS enabled). See [Obtain a TLS certificate](#obtain-a-tls-certificate) for more details.
93
93
3. Open the `443` port (or the port that you setin the `LISTEN_PORT` environment variable) on your server and make it reachable from the Internet.
94
-
4. Run the gateway:
95
-
94
+
4. To run all the required production structure you can execute the [start_prod_docker_environment.sh](./scripts/start_prod_docker_environment.sh) with the command:
95
+
96
+
```
97
+
./scripts/start_prod_docker_environment.sh
98
+
```
99
+
100
+
This script firstly generated the `telemetry/prometheus/prometheus-prod.yml` config file starting from the `telemetry/prometheus/prometheus-template.yml` (step required to perform the variable substitution) and then simply run the gateway with the following command:
101
+
96
102
```
97
-
docker compose -f docker-compose.yml -f docker-compose-prod.yml up
This command, similar to the local one, allows you to run a docker compose generated from 2 different docker compose files.
101
-
5. The Gateway will print its principal in the container logs, just as explained above.
106
+
5. To stop and clean all the local environment a bash script [stop_prod_docker_environment.sh](./scripts/stop_prod_docker_environment.sh) is provided. You can execute it with the command:
107
+
108
+
```
109
+
./scripts/stop_prod_docker_environment.sh
110
+
```
111
+
6. The Gateway will print its principal in the container logs, just as explained above.
102
112
103
113
### Obtain a TLS certificate
104
114
@@ -185,7 +195,11 @@ After installing Node.js and dfx, you can run the integration tests as follows:
185
195
```
186
196
./scripts/prepare_integration_tests.sh
187
197
```
188
-
2. The `tests/.env` file should now contain some variables created by `dfx`. Add the variables from the [.env.example](./tests/.env.example) file to the `.env` file and leave them unchanged.
198
+
2. Set the environment variables:
199
+
```
200
+
cp tests/.env.example tests/.env
201
+
```
202
+
When running the tests, the `tests/.env` file is modified by dfx, which will add some variables.
189
203
3. Run integration tests using the Rust test canister:
0 commit comments