*[Run **each** service using Docker](#run-each-service-using-docker)
*[Run **each** service using Python](#run-each-service-using-python)
3.[Start your testing with OpenCAPIF](#start-your-testing-with-opencapif)
> Capif services are developed under [services folder](https://labs.etsi.org/rep/ocf/capif/-/tree/main/services).
### Downloading the project
...
...
@@ -72,7 +61,7 @@ Usage: ./run.sh <options>
-m : Launch monitoring service
-h : show this help
```
This script builds and runs all services using docker images, including mongodb and nginx locally and in the background, and imports ca.crt to nginx. By default monitoring is not activated and Nginx is deployed use **capifcore** as a hostname.
This script builds and runs all services using docker images, including mongodb and nginx locally and in the background, and imports ca.crt to nginx. By default monitoring is not activated and Nginx is deployed use **capifcore** as a hostname.
Some examples of use:
```
...
...
@@ -87,6 +76,11 @@ Some examples of use:
```
> **IMPORTANT NOTE:** In some versions change of hostname in local deployment (setting some value different than ***capifcore***) creates wrong certificates on vault component. This prevents successful requests using the certificates. if this is your case, here is a little workaround to solve this issue meanwhile SDG is solving it:
> * Modify the hostname in the file ***capif/services/vault/vault_prepare_certs.sh*** on lines 43, 68, and 95.
> * Update the url parameter of the CCF from capifcore to the desired hostname in the file ***capif/services/register/config.yaml***.
If you want to check if all CAPIF services are running properly in a local machine after executing run.sh, you can use:
