@@ -440,10 +440,10 @@ At the beginning only some test data were stored in the DB. Step by step during
### Main technologies used
Since each layer runs in a separate Docker container each layer can and is build with a different technology. For that reason it makes sense to inspect each layer more detailed.
Since each layer runs in a separate Docker container each layer can and is build with a different technology. For that reason it makes sense to inspect each layer more detailed. All containers gets instantiated from a so called image which itself is builded from a Dockerfile. For that reason the main components in the Dockerfile are mentioned in the corresponding layer below.
### Front-end layer
Image for the container builds on TODO ...wichtigste images, libraries, technologies vom Dockerfile auflisten (Node.js image?)
Image for the container builds on a node.js image. Besides that Quasar and [NGINX](https://www.nginx.com/) gets installed too.
Inside the front-end following settings, libraries and technologies are used:
- Quasar
...
...
@@ -460,9 +460,8 @@ TODO falls weiter libraries einfach in package.json schauen
### Business layer
Image for the container builds on TODO ...wichtigste images, libraries, technologies vom Dockerfile auflisten (Python, GeoDjango?)
The main component of this container is a Python image besides many libraries and Poetry for package management. A script does check if the DB is already running and if this is the case it does start the setup for a successfull communication.
2. (Samuel)
Inside the business layer following settings, libraries and technologies are used:
- Django
- ORM of Django: Simplifies access to DB
...
...
@@ -474,15 +473,18 @@ Inside the business layer following settings, libraries and technologies are use
- osmviews: For QRanking
TODO falls weiter libraries einfach in poetry.lock schauen
Besides the API for the front-end also the SQL query for requesting data from the DB is defined in this layer. The query is comprised of different parts to getter all relevant data. The extend of the query is dictated by the number and types of the attributes of an applied filter. Finally the query joins and filters the DB tables and return the result to the business layer. Django turns the result list into a further processable format and finally returns it to the front-end.
### Database layer
TODO ganzes subkapitel
Image for the container builds on TODO ...wichtigste images, libraries, technologies vom Dockerfile auflisten (PostgreSQL, PostGis extension, ...)
- evtl andere tools um osmhistorydb-ch zum laufen zu bringen
The basis of this container is a PostgresQL image with the integrated [PostGis](https://postgis.net/) extension. PostGis enables the DB to handle geographic and geometry related objects. An extra script defines the DB properties and is the starting point to load all OSM relevant data into to DB.
Inside the database layer following settings, libraries and technologies are used:
- ...
- evtl auch was gemacht wurde: existing toolstack umschreiben!!!
The DB setup is inspired by [osmhistorydb-ch](https://github.com/sosm/osmhistorydb-ch).One of the main projects depending on this DB setup is [Project of the Month](https://wiki.openstreetmap.org/wiki/DE:Project_of_the_month_Switzerland) besides many others.
To use this setup some addditions, updates and changes to it regarding dependencies and versions were done.
TODO - evtl andere tools um osmhistorydb-ch zum laufen zu bringen
TODO Inside the database layer following settings, libraries and technologies are used:
TODO - evtl auch was gemacht wurde: existing toolstack umschreiben!!!
