Flask Web Server

Introduction

In our development environment, there will likely be times when we are running our back-end REST services, like Flask, that our application relies on to get its data from. In production, we would conventionally have a public-facing web server that responds to all requests for our application. It would then forward, or proxy, incoming requests for the back-end services onto an application server hosting Flask that is not public-facing. Locally, while we could just run the Parcel web server and the Flask web server on two different ports, it’s much cleaner if we get one of them to proxy the other as we would in a production setting. This saves us from messing around with cross-origin resource sharing or port mapping.