Analyst

This article provides a guide to deploying the analyst components of Confidential Computing.

Prerequisites

Before deploying any component make sure you have completed the analyst sections in the getting started guide

There is considerable overlap between the components required for an analyst and a data provider. If you have already deployed the data provider components, you can skip ahead to the analyst frontend section.

Warning

If you have not deployed the data provider components, you must first complete steps 1-4 in the data provider deployment guide before continuing on this guide.

Analyst Frontend

The data provider frontend is a web interface to interact with Confidential Computing as a Data Provider. It allows data providers to create, edit, and submit analyses.

Populate Configuration File

Fill in the following configuration in the analyst-frontend/conf/config.js file created in the storage configuration step:

    const CONFIG = {
        serverType: 'ANALYST', // (1)!
        confidentialComputing: {
            authenticationUrl: 'cc-authencation:8061', // (2)!
            keyManagementUrl: 'cc-key-management:8051', // (3)!
            backendUrl: 'cc-backend:8031', // (4)!
            chainId: 'Partisia Confidential Computing',
            dataCatalogContract: 'DATA_CATALOG_CONTRACT_ADDRESS', // (5)!
            analysisContract: 'ANALYSIS_CONTRACT_ADDRESS', // (6)!
        },
        vprTheme: {
            primaryColor: '#FF6E01', // (7)!
            secondaryColor: '#2B2F33', // (8)!
            organizationIcon: 'ORGANIZATION_ICON_PATH', // (9)!
            windowsTitle: 'Confidential Computing Analyst', // (10)!
        },
    }

Specifies the type of frontend. Should always be ANALYST
The local URL to communicate with the authentication service for users to log in.
The local URL to communicate with the Key Management service to sign transactions.
The local URL to communicate with the Backend.
Address of the smart contract that stores Data Catalog metadata.
Address of the smart contract that merges analyses.
Primary color for the frontend theme.
Secondary color for the frontend theme.
Path to the organization logo image. - It should be a path in the mapped Docker container to the image logo file from the storage step.
Title to be displayed in the web browser tab.

Docker Configuration

In addition, you must configure the analyst frontend docker image by adding the following to your docker-compose.yml file:

Click to expand: Analyst Frontend - Example Docker Configuration

services:
  confidential-computing-analyst-frontend:
    container_name: cc-analyst-frontend
    image: registry.gitlab.com/secata/confidential-computing/frontend/coordinator:latest
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - /path/to/analyst-frontend/conf:/usr/share/nginx/html/conf

The bound port is where the Analyst Frontend will be available. Using the example configuration, it will be available at http://cc-analyst-frontend:8080 on the host network.

The path of the mapped volume must correspond to the analyst frontend folder created in the storage step.

Deploy the Component

Open your terminal and navigate to the directory containing yourdocker-compose.yml file.
Execute the following Docker Compose command to start the Authentication Service container:
```
docker-compose up -d confidential-computing-analyst-frontend
```
Check the logs of the authentication container to ensure it is running without errors:
```
docker logs -f cc-analyst-frontend
```