Skip to content
Snippets Groups Projects
Commit fe91ce6a authored by Christian Boettcher's avatar Christian Boettcher
Browse files

changed to english spelling where no technical reason prevents it

parent b76a25d0
No related branches found
No related tags found
No related merge requests found
# DataCatalog # Datacatalogue
This is Data Catalog for eFlows4HPC project This is Data Catalogue for eFlows4HPC project
This work has been supported by the eFlows4HPC project, contract #955558. This project has received funding from the European High-Performance Computing Joint Undertaking (JU) under grant agreement No 955558. The JU receives support from the European Union’s Horizon 2020 research and innovation programme and Spain, Germany, France, Italy, Poland, Switzerland, Norway. This work has been supported by the eFlows4HPC project, contract #955558. This project has received funding from the European High-Performance Computing Joint Undertaking (JU) under grant agreement No 955558. The JU receives support from the European Union’s Horizon 2020 research and innovation programme and Spain, Germany, France, Italy, Poland, Switzerland, Norway.
...@@ -12,9 +12,9 @@ The project has recieved funding from German Federal Ministry of Education and R ...@@ -12,9 +12,9 @@ The project has recieved funding from German Federal Ministry of Education and R
Find architecture in [arch](arch/arch.adoc) folder. Find architecture in [arch](arch/arch.adoc) folder.
## Frontend Server for the Data Catalog ## Frontend Server for the Data Catalogue
[This](frontend/) part is the frontend for the Data Catalog. It will be the user interface, so that no one is forced to manually do http calls to the api. Since the content is managed by the [api-server](apiserver/), this can be deployed as a static website, containing only html, css and javascript. To make the different pages more uniform and avoid duplicate code, the static pages will be generated by the [jinja2](https://jinja.palletsprojects.com/en/3.0.x/templates/) template engine. [This](frontend/) part is the frontend for the Data Catalogue. It will be the user interface, so that no one is forced to manually do http calls to the api. Since the content is managed by the [api-server](apiserver/), this can be deployed as a static website, containing only html, css and javascript. To make the different pages more uniform and avoid duplicate code, the static pages will be generated by the [jinja2](https://jinja.palletsprojects.com/en/3.0.x/templates/) template engine.
To compile the static pages to the `./site/` directory (will be created if required), simply run To compile the static pages to the `./site/` directory (will be created if required), simply run
```bash ```bash
...@@ -30,9 +30,9 @@ python -m http.server <localport> --directory site/ ...@@ -30,9 +30,9 @@ python -m http.server <localport> --directory site/
``` ```
The python http.server package should **not** be used for deployment, as it does not ensure that current security standards are met, and is only intended for local testing. The python http.server package should **not** be used for deployment, as it does not ensure that current security standards are met, and is only intended for local testing.
## API-Server for the Data Catalog ## API-Server for the Data Catalogue
[This](apiserver/) part is the the API-server for the Data Catalog, which will provide the backend functionality. [This](apiserver/) part is the the API-server for the Data Catalogue, which will provide the backend functionality.
It is implemented via [fastAPI](https://fastapi.tiangolo.com/) and provides an api documentation via openAPI. It is implemented via [fastAPI](https://fastapi.tiangolo.com/) and provides an api documentation via openAPI.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment