Skip to content

rerodrigues/flight-map

Repository files navigation

Flight Maps BR

An interactive map of all flights from/to every Brazilian airport

Live demo

Usage

Create a file in the root of the project called .env.local with the the paths of the datafiles

The following config should work, however I recommend hosting the datafiles yourself. (thx @hugosenari for the datafiles)

REACT_APP_AIRPORTS_URL=https://raw.githubusercontent.com/hugosenari/voos/master/data/airports.json
REACT_APP_FLIGHTS_URL=https://raw.githubusercontent.com/hugosenari/voos/master/data/voos.json

Then, in the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

All available additional scripts

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Motivation and Goals

Despite being fully functional and the data displayed being real, this project was conceived to be a playground to test new technologies, especially the new versions/replacements of the technologies that I and my team use on our daily projects. It was never intended to be a finished product, serving as a more flexible and less critic environment to test new libs, patterns and paradigms while still fully functional. The main goal here is to validate the viability of implementing these discoveries into our projects, while learning from them.

Technologies used


2020 - Renato Rodrigues - No rigths reserved