https://github.com/flightaware/alerts_frontend
Frontend Alerts service for FlightAware's AeroAPI
https://github.com/flightaware/alerts_frontend
flightaware-aeroapi-service
Last synced: about 1 month ago
JSON representation
Frontend Alerts service for FlightAware's AeroAPI
- Host: GitHub
- URL: https://github.com/flightaware/alerts_frontend
- Owner: flightaware
- License: bsd-3-clause
- Created: 2022-06-15T22:13:30.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-08-08T22:05:28.000Z (almost 4 years ago)
- Last Synced: 2023-04-18T10:34:08.672Z (about 3 years ago)
- Topics: flightaware-aeroapi-service
- Language: JavaScript
- Homepage:
- Size: 1.28 MB
- Stars: 2
- Watchers: 18
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Alerts Frontend - A sample frontend for the FlightAware Data API for alerts
## QuickStart
Unlike the FIDS Frontend website, the alerts frontend is intended only for the AeroAPI backend service, Aero Apps. Head
over to [AeroAPI](https://github.com/flightaware/aeroapps) and follow the quickstart guide there for the alerts backend
section. The documented commands will pull this Alerts Frontend as a ready to use Docker container that will present
flight data from the Aero Apps alerts backend.
## alerts-frontend
FlightAware Alerts is a small webapp powered by a backend like the alerts-backend service in FlightAware Aero Apps.
You can use it to enter in parameters to create an alert for your FlightAware account. In this webapp, the parameters
that one can input are ident, origin, destination, the aircraft type, the start date of the alert, and the end date
of the alert.
This service is intended to be run in the context of a service like the Aero Apps alerts section. The nginx proxy
configuration assumes there will be a locally available service at the "alerts-backend" hostname. If running the
alerts-frontend as a stand-alone service the nginx proxy_pass configuration will need to be changed to point to the
location of your backend service.
Once running, the service is accessible at http://localhost:8080 in your web browser (if not running Docker locally, use
the Docker host's address).