dschick/BreCal
dschick/BreCal
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Bremen calling
This repository has been archived on 2025-02-17. You can view files and clone it, but cannot push or open issues or pull requests.
173 Commits 57 Branches 66 Tags 5.6 MiB
feature/shipcall_validation
Go to file
max_metz b87aa23e28 shipcall evaluation now also supports a shipcall_id argument, so only a single Shipcall is evaluated. Updating requirements.txt after installing the virtual environment for the first time on a Windows laptop. Updating the berth-stub according to the recent berth changes (owner id & authority id).
2023-10-13 12:23:27 +02:00
.vscode initial commit 2023-09-08 06:09:24 +02:00
docs adding more variable names in the xlsx file 2023-09-08 22:30:21 +02:00
misc merged participant type for assignment side quest 2023-10-09 18:02:02 +02:00
src shipcall evaluation now also supports a shipcall_id argument, so only a single Shipcall is evaluated. Updating requirements.txt after installing the virtual environment for the first time on a Windows laptop. Updating the berth-stub according to the recent berth changes (owner id & authority id). 2023-10-13 12:23:27 +02:00
.gitignore merging 'lib_brecal_utils' into the develop branch. This includes the traffic light status (release 1.0) and preparation for input validation (later release). Extended the requirements.txt to include numpy, pandas and sqlalchemy. There may be some more adaptations to the requirements.txt soon 2023-10-12 16:03:31 +02:00
Ampelfunktion.md merging 0.7.0 fixed 2023-10-12 15:54:15 +02:00
change_log_metz.md shipcall evaluation now also supports a shipcall_id argument, so only a single Shipcall is evaluated. Updating requirements.txt after installing the virtual environment for the first time on a Windows laptop. Updating the berth-stub according to the recent berth changes (owner id & authority id). 2023-10-13 12:23:27 +02:00
environment.yml shipcall evaluation now also supports a shipcall_id argument, so only a single Shipcall is evaluated. Updating requirements.txt after installing the virtual environment for the first time on a Windows laptop. Updating the berth-stub according to the recent berth changes (owner id & authority id). 2023-10-13 12:23:27 +02:00
README.md initial commit 2023-09-08 06:09:24 +02:00

README.md

Bremen Calling

Projekt zur verbesserten Kommunikation der maritimen Partner bei Schiffsanläufen in Bremen.

Anforderungen

Architektur

Die Architektur besteht aus einer Datenbank und einem in Python implementierten Backend, das eine API zu Verfügung stellt. Diese API ist als OpenAPI 3.0 spezifiziert. Die Anwendung selbst kommuniziert nur über diese API mit der Datenbank. Es sind damit unterschiedliche Anwendungsplattformen denkbar, etwa eine Web-, Mobile- oder Windows Desktop Anwendung. In dieser Folie ist ein Bild / Überblick enthalten.

Ein erster Gedanke des Datenbank-Layouts sieht folgendermaßen aus: image

Entwicklung

Postman

Zum Debuggen der Flask App verwende ich dieses Tutorial: https://code.visualstudio.com/docs/python/tutorial-flask#_create-a-project-environment-for-the-flask-tutorial