v2.3.0

AeroApps v2.3.0 adds an endpoint for the alerts backend that can be used in the alerts frontend service to delete configured alerts. Given an AeroAPI alert ID, it uses that ID to delete the configured alert from AeroAPI's system, and also from the SQLite alert configuration table volume mounted in the Docker image. There are also more minor bug fixes and clarifications in the README for the alerts section in this feature.

v2.2.0

AeroApps v2.2.0 adds two endpoints for the alerts backend to send to the alerts frontend service - one sends the data from the SQLite table storing the alert configurations to be displayed on an alert configuration table, and the other sends the data from the other SQLite table storing the POSTed alerts sent from AeroAPI. There are also some minor bug fixes and formatting changes for the alerts section in this feature.

v2.1.0

AeroApps v2.1.0 adds an endpoint for the Python alerts backend service. This feature allows AeroAPI to, when an alert is triggered, send a POST request to the endpoint with information about the triggered alert. It will also store these triggered alerts in an SQLite database mounted as a Docker volume.

v2.0.0

AeroApps v2 adds Python backend service that showcases handling alerts. This feature allows one to create alert configurations that can be viewed using the new Alerts Frontend service, and will store those alert configurations in an SQLite database mounted as a Docker volume.

v1.0.0

AeroApps v1 contains a Python and a Java example backend services that are functionally equivalent. With these components flights can be tracked at various airports using FlightAware AeroAPI and view them using the FIDS Frontend service.