devicehub-teal/README.md

# Devicehub

Devicehub is a distributed IT Asset Management System focused on reusing digital devices, created under the [eReuse.org](https://www.ereuse.org) initiative.

This README explains how to install and use Devicehub. [The documentation](http://devicehub.ereuse.org) explains the concepts, usage and the API it provides.

Devicehub is built with [Teal](https://github.com/ereuse/teal) and [Flask](http://flask.pocoo.org). 

Devicehub relies on the existence of an [API_DLT connector](https://gitlab.com/dsg-upc/ereuse-dpp) verifiable data registry service, where specific operations are recorded to keep an external track record (ledger).

# Installing
Please visit the [Manual Installation](README_MANUAL_INSTALLATION.md) instructions to understand the detailed steps to install it locally or deploy it on a server. However, we recommend the following Docker deployment process.

# Docker
There is a Docker compose file for an automated deployment. Two instances of DeviceHub will be deployed. The following steps describe how to run and use it.

1. Download the sources:
```
  git clone https://github.com/eReuse/devicehub-teal.git -b oidc4vp
  cd devicehub-teal
```

2. If you want to initialise one of DeviceHub instances (running on port 5000) with sample device snapshots, copy it/them into that directory. e.g.
```
  cp snapshot01.json examples/snapshots/
```

 Otherwise, the device inventory of your DeviceHub instance will be empty and ready to add new devices. For that (no snapshot import), you need to change the var to 'n' in the **.env** file
```
  IMPORT_SNAPSHOTS='n'
```

To register new devices, the [workbench software](https://github.com/eReuse/workbench) can be run on a device to generate its hardware snapshot that can be uploaded to one of the two DeviceHub instance.

3. Setup the environment variables in the .env file.  You can find one example in examples/env.example.
If you don't have any, you can copy that example and modify the basic vars
```
  cp examples/env.example .env
```
You can use these parameters as default for a local test, but default values may not be suitable for an internet-exposed service for security reasons. However, these six variables need to be initialised:
```
  API_DLT
  API_DLT_TOKEN
  API_RESOLVER
  ABAC_TOKEN
  ABAC_USER
  ABAC_URL
  SERVER_ID_FEDERATED
  CLIENT_ID_FEDERATED
```
The first six values should come from an already operational [API_DLT connector](https://gitlab.com/dsg-upc/ereuse-dpp) service instance.

For the last two values check [manual install step 9]('https://github.com/eReuse/devicehub-teal/blob/oidc4vp/README_MANUAL_INSTALLATION.md#installing') for more details.

4. Build and run the docker containers:
```
  ./launcher.sh
```
To stop these docker containers, you can use Ctl+C. You'll maintain the data and infrastructure state if you run "compose up" again.

On the terminal screen, you can follow the installation steps. If there are any problems, error messages will appear here. The appearance of several warnings is normal and can be ignored.

If the last line you see one text like this, *exited with code*:
```
  devicehub-teal-devicehub-id-client-1 exited with code 1
```
means the installation failed.

If the deployment was end-to-end successful (two running Devicehub instances successfully connected to the DLT backend selected in the .env file), you can see this text in the last lines:
```
  devicehub-teal-devicehub-id-client-1  |  * Running on http://172.28.0.2:5000/ (Press CTRL+C to quit)
  devicehub-teal-devicehub-id-server-1  |  * Running on all addresses.
  devicehub-teal-devicehub-id-server-1  |    WARNING: This is a development server. Do not use it in a production deployment.
  devicehub-teal-devicehub-id-server-1  |  * Running on http://172.28.0.5:5000/ (Press CTRL+C to quit)
```

That means the two Devicehub instances are running in their containers, which can be reached as http://localhost:5000/ and http://localhost:5001/

Once the DeviceHub instances are running, you might want to register a user binding to the DLT with the following commands (here, it assumes you want to execute it on devicehub-id-client, you might also want to do it in devicehub-id-server). Change the variables accordingly

```
  FILE=my_users_devicehub.json
  DOCKER_SERVICE=devicehub-id-server
  docker compose cp /path/to/${FILE} ${DOCKER_SERVICE}:/tmp/
  docker compose exec ${DOCKER_SERVICE} flask dlt_register_user /tmp/${FILE}
```

**my_users_devicehub.json** is a custom file which is similar to the one provided in `examples/users_devicehub.json`

5. To shut down the services and remove the corresponding data, you can use:
```
  docker compose down -v
```

If you want to enter a shell inside a **new instance of the container**:
```
  docker run -it --entrypoint= ${target_docker_image} bash
```

If you want to enter a shell on an **already running container**:
```
  docker exec -it ${target_docker_image} bash
```

To know the valid value for ${target_docker_image} you can use:
```
  docker ps
```

6. These are the details for use in this implementation:

  Devicehub with URL (http://localhost:5000) is the identity provider of OIDC and have a user defined in **.env** file with SERVER_ID_EMAIL_DEMO var.

  Devicehub with URL (http://localhost:5001) is the client identity of OIDC and have a user defined in **.env** file with SERVER_ID_EMAIL_DEMO var.

  You can change these values in the *.env* file

7. If you want to use Workbench for these DeviceHub instances, you need to go to
```
  http://localhost:5001/workbench/
```
with the demo user and then download the settings and ISO files. Follow the instructions on the [help](https://help.usody.com/en/setup/setup-pendrive/) page.