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

List of links removed from bottom and added adequately at each of the elements. One phrase slightly changed, but same public information is released.

Porras-Bernardez 2023-11-29 08:24:37 +00:00
parent 0e5860f30c
commit e410215eac
1 changed files with 4 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
Technical-infrastructure.md

@ -4,7 +4,7 @@ In order to comply with international metadata standards such as Dublin Core, Da
The new editorial system of the repository on the server side, which is also known as [tethys.backend](https://gitea.geologie.ac.at/geolba/tethys.backend), is a web-based open-source software that operates directly on the PostgreSQL database. It is built using AdonisJS, which is a Node.js-based web framework that provides a robust set of tools and features for building scalable and secure web applications. AdonisJS also includes an object-relational mapper (ORM) that allows developers to work with database tables and records using object-oriented programming techniques. The styling of the Tethys RDR backend is built using Tailwind, which is a utility-first CSS framework. The new editorial system of the repository on the server side, which is also known as [tethys.backend](https://gitea.geologie.ac.at/geolba/tethys.backend), is a web-based open-source software that operates directly on the PostgreSQL database. It is built using AdonisJS, which is a Node.js-based web framework that provides a robust set of tools and features for building scalable and secure web applications. AdonisJS also includes an object-relational mapper (ORM) that allows developers to work with database tables and records using object-oriented programming techniques. The styling of the Tethys RDR backend is built using Tailwind, which is a utility-first CSS framework.
General descriptions of the systems and software used can be found in our Wiki [6]. There, it is possible to find public information about the database model, instructions for starting Docker container and a data architecture diagram for a clear understanding of all storage locations. All code repositories are accessible online via a Gitea instance [7] hosted at the GeoSphere Austria data centre. The associated Tethys RDR Docker images are also securely stored there using the built-in Docker registry functionality [8]. All necessary configurations to launch the Docker container are described in the Wiki. General descriptions of the systems and software used can be found in our [Wiki](https://gitea.geologie.ac.at/geolba/tethys.backend/wiki/?action=_pages). There, it is possible to find public information about the database model, instructions for starting Docker container and a data architecture diagram for a clear understanding of all storage locations. All code repositories are accessible online via a [Gitea instance](https://gitea.geologie.ac.at) hosted at the GeoSphere Austria data centre. The associated Tethys RDR Docker images are also securely stored there using the built-in Docker registry [functionality](https://gitea.geologie.ac.at/geolba/-/packages). All necessary configurations to launch the Docker container are described in the Wiki.
Internal information about virtual server, maintenance and security settings are stored in a separate, private wiki on internal LAN servers. Internal information about virtual server, maintenance and security settings are stored in a separate, private wiki on internal LAN servers.
@ -12,9 +12,9 @@ Hardware infrastructure is generally renewed every 3-4 years, which is transpare
GeoSphere Austria acts according to international IT standards for information security management. Compliance with these standards is monitored by the organization and ongoing audits are carried out as an ongoing process to ensure relevant standards are met. GeoSphere Austria acts according to international IT standards for information security management. Compliance with these standards is monitored by the organization and ongoing audits are carried out as an ongoing process to ensure relevant standards are met.
All the software components used for the three-tiered client/server architecture in the Tethys RDR are versioned through GIT and can be accessed online via a Gitea instance [9] hosted by the computer centre of GeoSphere Austria. The frontend can be accessed at [10], the backend at [11], and the API at [12]. All the software components used for the three-tiered client/server architecture in the Tethys RDR are versioned through GIT and can be accessed online via a [Gitea instance](https://gitea.geologie.ac.at) hosted by the computer centre of GeoSphere Austria. [Frontend](https://gitea.geologie.ac.at/geolba/tethys.frontend), [backend](https://gitea.geologie.ac.at/geolba/tethys.backend) and [API](https://gitea.geologie.ac.at/geolba/tethys.api) are also accessible.
The Tethys RDR 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 [13], which is always triggered whenever new code is committed to the repository's backend. The Tethys RDR 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/runs/5), which is always triggered whenever new code is committed to the repository's backend.
--- ---
@ -52,19 +52,4 @@ There are several processes that are used to monitor and manage the need of tech
- Continuous integration/continuous delivery (CI/CD): These are practices that involve automating the building, testing, and deployment of software. This helps to catch errors and ensure that changes are released into production environments as quickly and reliably as possible. - Continuous integration/continuous delivery (CI/CD): These are practices that involve automating the building, testing, and deployment of software. This helps to catch errors and ensure that changes are released into production environments as quickly and reliably as possible.
- Agile methodologies: Agile development focuses on iterative development cycles, with frequent feedback and collaboration between developers, stakeholders, and end-users. This approach helps ensure that software development stays aligned with changing requirements and priorities. - Agile methodologies: Agile development focuses on iterative development cycles, with frequent feedback and collaboration between developers, stakeholders, and end-users. This approach helps ensure that software development stays aligned with changing requirements and priorities.
---
References:
[1] https://gitea.geologie.ac.at/geolba/tethys.frontend
[2] https://gitea.geologie.ac.at/geolba/tethys.api
[3] https://www.tethys.at/oai?verb=ListMetadataFormats
[4] https://www.tethys.at/oai?
[5] https://gitea.geologie.ac.at/geolba/tethys.backend
[6] https://gitea.geologie.ac.at/geolba/tethys.backend/wiki/?action=_pages
[7] https://gitea.geologie.ac.at
[8] https://gitea.geologie.ac.at/geolba/-/packages
[9] https://gitea.geologie.ac.at
[10] https://gitea.geologie.ac.at/geolba/tethys.frontend
[11] https://gitea.geologie.ac.at/geolba/tethys.backend
[12] https://gitea.geologie.ac.at/geolba/tethys.api
[13] https://gitea.geologie.ac.at/geolba/tethys.backend/actions/runs/5