geolba/tethys.backend
2
1
Fork 1
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

- C15-Technical-Infrastructure.md

Kaimbacher 2023-05-25 10:46:05 +02:00
parent 7c276b311b
commit f276d0f1ae
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
C15-Technical-Infrastructure.md

@ -22,7 +22,7 @@ Compliance with international standards in IT is monitored and checked by the or
## C15.4. The version control systems used for repository generated software.
All the software components used for the three-tiered client/server architecture in the TEHYS research data repository are versioned through GIT and can be accessed online via a [Gitea instance] (https://gitea.geologie.ac.at) hosted by the computer center of GeoSphere Austria. The frontend can be accessed at https://gitea.geologie.ac.at/geolba/tethys.frontend, the backend at https://gitea.geologie.ac.at/geolba/tethys.backend, and the API at https://gitea.geologie.ac.at/geolba/tethys.api.\
All the software components used for the three-tiered client/server architecture in the TEHYS research data repository are versioned through GIT and can be accessed online via a [Gitea instance](https://gitea.geologie.ac.at) hosted by the computer center of GeoSphere Austria. The frontend can be accessed at https://gitea.geologie.ac.at/geolba/tethys.frontend, the backend at https://gitea.geologie.ac.at/geolba/tethys.backend, and the API at https://gitea.geologie.ac.at/geolba/tethys.api.\
The TETHYS research repository is being developed using the **Continuous Integration/Continuous Deployment (CI/CD)** practice, which involves frequent testing and deployment of code changes to production. Whenever new code is published, automatic tests run in the background (CI), and when new versions are released, new Docker images are automatically deployed (CD). This entire process is implemented using Gitea Actions, a powerful platform that enables automation of various tasks like building, testing, and deploying code, as well as sending notifications such as alerts for failed tests. All workflows are defined in YAML files, such as the [ci.yaml file](https://gitea.geologie.ac.at/geolba/tethys.backend/actions?workflow=ci.yaml&state=closed), which is always triggered whenever new code is committed to the TETHYS backend.
## C15.5 Measures taken to ensure that availability, bandwidth, and connectivity are sufficient to meet the needs of the designated community.