Skip to content
Snippets Groups Projects
Commit 6276aba3 authored by Jorge Moratinos's avatar Jorge Moratinos
Browse files

Merge branch...

Merge branch 'OCF-Doc26-include-workaround-for-local-deployment-with-different-hostname' into 'develop'

Resolve "Include workaround for local deployment with different hostname"

Closes #26

See merge request !30
parents cb22ae2f 5ab42c11
1 merge request!30Resolve "Include workaround for local deployment with different hostname"
Pipeline #11761 passed with stage
in 31 seconds
# How to Run
1. [Downloading the project](#downloading-the-project)
1. [Create a folder to download the project](#1-create-a-folder-to-download-the-project)
2. [Download the deployment script](#2-download-the-deployment-script)
3. [Run the deployment script](#3-run-the-deployment-script)
2. Run the services
* [Run **all** CAPIF Services locally with Docker images](#run-all-capif-services-locally-with-docker-images)
* [Run **all** CAPIF Services locally with Docker images *and deploy monitoring stack*](#run-all-capif-services-locally-with-docker-images-and-deploy-monitoring-stack)
* [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:
```
./check_services_are_running.sh
......
......@@ -102,7 +102,10 @@ To run more specific tests, for example, only one functionality:
"capif_api_logging_service",
"capif_api_provider_management",
"capif_api_publish_service",
"capif_security_api
"capif_security_api",
"api_status",
"vendor_extensibility",
"smoke"
And Run:
docker run -ti --rm --network="host" \
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment