trustchain-oc1-orchestral/idhub-docker
Archived
10
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Edits on ereuse pilot and misc tweaks

Browse source
This commit is contained in:
leandro@ac.upc.edu 2024-04-04 07:25:38 +02:00
parent d9775501ad
commit bb5399c275
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
README.md
View file

@ -8,7 +8,7 @@
- Instances:
- https://idhub1-xo9b.demo.pangea.org
- https://idhub2-xo9b.demo.pangea.org
- Motivation: The aim is to support an accreditation program for vulnerable people, exploring the value of using verifiable credentials to get services/benefits.
- Motivation: Support an accreditation program for vulnerable people, exploring the value of using verifiable credentials to get services/benefits.
- Scenario: A vulnerable family obtains a benefit (internet connection fee discount) by presenting a verifiable credential to a connectivity provider entity.
Actors-> **XO9B**: IdHub1 (acting as a user wallet for families holding credentials issued by a social support organisation), **Connectivity provider entity**: Demo portal, IdHub2 (acting as verifier). The verifier portal incorporates verification capabalities and support to establish an OIDC4VP dialog with the user wallet for credential presentation (accreditation).
@ -22,7 +22,7 @@
- **Lafede**:
- Instance:
- https://idhub1-lafede.demo.pangea.org
- Motivation: Implementation of dual EIDAS1 and EIDAS2 compliant attestations as signed PDFS with public verifiable credentials exported as QR codes embedded in these documents. Member organisations and related persons of the Lafede federation request membership and training certificates.
- Motivation: Implementation of dual eIDAS1 and eIDAS2 compliant attestations as signed PDFS with public verifiable credentials exported as QR codes embedded in these documents. Member organisations and related persons of the Lafede federation request membership and training certificates.
Actors-> **Lafede**: idHub
@ -46,10 +46,10 @@
- https://idhub1-ereuse.demo.pangea.org
- https://idhub2-ereuse.demo.pangea.org
- https://devicehub.demo.pangea.org
- Motivation: TODO
- Scenarios: TODO
- Motivation: In the circular economy scenario of eReuse, devices change hands, and their hardware composition changes due to repair or upgrades. Hardware changes during processes known as repair, refurbishment, or remanufacturing. The circular economy requires access to trusted and verifiable second-hand computer product information (inventory, datasheet), which qualified actors manage. This is the case with recyclers and refurbishers or remanufacturers that modify devices.
- Scenarios: When a product registered in an inventory service is brought to an actor that changes the hardware (upgrade or dematerialisation), staff from that actor will want to report in that inventory the hardware change performed. Staff persons from a hardware company (Organisation R) can access the "Inventory service D" (DeviceHub instance where a given device is registered in its inventory). This can be achieved by accessing the product page (the URL for that item that constitutes a digital product passport or DPP) of that product item presenting the appropiate credentials.
- **generic**: https://idhub.demo.pangea.org
- Motivation: For demo purposes, for showing other people different than the intended pilot what we do. It is currently similar to lafede pilot
- Motivation: For demo purposes, for showing other people different than the intended pilot what we do. It is currently similar to Lafede pilot.
### Instances
@ -78,12 +78,12 @@
### Details on localhost config
You can test all the features in localhost. It was tested on Debian GNU/Linux 12 (bookworm)
All features can be tested in localhost. It was tested on Debian GNU/Linux 12 (bookworm)
- on host machine install nginx and docker
- On host machine install nginx and docker.
- nginx acts as a reverse proxy is used to get into docker containers (same approach applies to deployed pilots and instances)
- see [nginx-localhost.site](./nginx-localhost.site) for the nginx site config
- add at the end of `/etc/hosts` a line with: `127.0.0.1 idhub2 idhub3` so you make work the DNS resolution locally
- See [nginx-localhost.site](./nginx-localhost.site) for the nginx site config
- Add at the end of `/etc/hosts` a line with: `127.0.0.1 idhub2 idhub3` so you make the DNS resolution work locally.
## Installation
@ -99,11 +99,11 @@ Execute `./build__all.sh` to run all the pilots, that includes building locally
Or run a specific pilot with `./build__pilot-example.sh`.
All the scripts are written in POSIX Shell. I hope they are easy enough and structured to be adapted to your needs.
All the scripts are written in POSIX Shell. We hope they are easy enough and structured to be adapted to your needs.
## Development
You can use these docker images for developing the software. This repo is targeted on integrating, deploying and testing the IdHub tools. You can do the same with the other tools, the trick used is to override the docker's directory with a local directory. Example found on all pilots instances.
You can use these Docker images for developing the software. This repo is targeted on integrating, deploying and testing the IdHub tools. You can do the same with the other tools, the trick used is to override the docker's directory with a local directory. Example found on all pilots instances.
```yaml
volumes:
@ -116,13 +116,13 @@ In the `.env` there are some variables intended to be used for debugging purpose
### Commands that you might like
if you want to enter a shell inside a new container:
If you want to enter a shell inside a new container:
```sh
docker run -it --entrypoint= ${target_docker_image} bash
```
if you want to enter a shell on already running container:
If you want to enter a shell on already running container:
```sh
docker exec -it ${target_docker_image} bash