GAID

Please enter the google analytics ID for appData file.

Gain insights into using Python and Transcrypt to build complete web applications. Delve into refactoring, adding new features, and creating cohesive frontend-backend projects with React.

tarball.tar.gz

Final_App

ReactPythonStep01

ReactPythonStep02

ReactPythonStep03

ReactPythonStep04

ReactPythonStep05

ReactPythonStep06

ReactPythonStep07

ReactPythonStep08

ReactPythonStep09

ReactPythonStep10

ReactPythonStep11

ReactPythonStep12

ReactPythonStep13

FinalWebApp

Gunicorn_run

ReactPythonStep01-copy

Python is already used in the backend of most web applications, but sadly it does not work with web browsers to drive the frontend of those applications. Transcrypt can help by creating more coherent web-based projects, using Python to write both the backend and the frontend.

This course builds on the lessons in Using the Python Transcrypt Transipler for Front-end Coding to implement a complete React and Python web-based project. In each chapter, we will refactor existing code to add new functionality, building up the application as you go. Each chapter ends with a running application that includes all of the features we added up to that specific point.

Using Python and Transcrypt to Build a Complete Web Application

## What is WSGI?
WSGI stands for **Web Server Gateway Interface**, a specification describing how a web server communicates with web applications. It helps to separate the application-specific tasks that a web application performs from more generic tasks that are required to serve up web content.   Web frameworks like Flask and Django, have implemented this specification so they are able to properly communicate with popular web servers.

---

## Warning with Werkzeug development server

For convenience, Flask comes with the Werkzeug development application server that might be used frequently during the development process.  One thing you may have noticed when that development server starts up is a warning message:


>**WARNING**: This is a development server. Do not use it in a production  
    deployment.  Use a production WSGI server instead.

---

## The WSGI containers

The development server was not designed to be particularly secure, efficient, or stable and should not be used for production.  Instead, we have one of the several WSGI containers out there that have actually been designed for production use.  Some of the more common ones are: 

* Gunicorn
* Phusion Passenger
* uWSGI
* Waitress
* Apache mod_wsgi

Which WSGI container should be used will be largely dependent on how much configurability is desired and what operating system platform we are running on. When we have a Flask application, one of the most common pairings of a web server and a WSGI container, is to use NGINX and Gunicorn.  We'll look at demonstrations using those, but you should know that these are intended to run in a Linux environment.

>**Note:** On Windows, we have fewer options. The most common use is the Apache web server with mod_wsgi, or possibly the IIS web server with Waitress as the WSGI container. While the setup for each combination is going to be more specific, the basic concept of how it works will be the same as what will be demonstrated with NGINX and Gunicorn.

# What is WSGI?
WSGI stands for **Web Server Gateway Interface**, a specification describing how a web server communicates with web applications. It helps to separate the application-specific tasks that a web application performs from more generic tasks that are required to serve up web content.   Web frameworks like Flask and Django, have implemented this specification so they are able to properly communicate with popular web servers.

---

# Warning with Werkzeug development server

For convenience, Flask comes with the Werkzeug development application server that might be used frequently during the development process.  One thing you may have noticed when that development server starts up is a warning message:


>**WARNING**: This is a development server. Do not use it in a production  
    deployment.  Use a production WSGI server instead.

---

# The WSGI containers

The development server was not designed to be particularly secure, efficient, or stable and should not be used for production.  Instead, we have one of the several WSGI containers out there that have actually been designed for production use.  Some of the more common ones are: 

* Gunicorn
* Phusion Passenger
* uWSGI
* Waitress
* Apache mod_wsgi

Which WSGI container should be used will be largely dependent on how much configurability is desired and what operating system platform we are running on. When we have a Flask application, one of the most common pairings of a web server and a WSGI container, is to use NGINX and Gunicorn.  We'll look at demonstrations using those, but you should know that these are intended to run in a Linux environment.

>**Note:** On Windows, we have fewer options. The most common use is the Apache web server with mod_wsgi, or possibly the IIS web server with Waitress as the WSGI container. While the setup for each combination is going to be more specific, the basic concept of how it works will be the same as what will be demonstrated with NGINX and Gunicorn.

Explore more about WSGI containers in this lesson.

Introduction

Environment Setup

Landing Page

Modal View

REST Service

Build a REST API in Flask

Books

Menus

User Login

Lookups

User Context

Editing Lookups

Filtering Data

Editing Books

SPA Redirect

Deploying the Application

Conclusion

WSGI Container

What is WSGI?